Make x-transition delay syntax consistent with duration syntax #3476
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey there,
I noticed that with x-transition.duration it was possible to use a x-transition.duration.500ms syntax as well as x-transition.duration.500 (as also noted in the source code). For x-transition.delay only the ms syntax was possible. This PR makes the delay syntax consistent with the duration syntax, so both work with or without the ms suffix.
@joshhanley Re-opened this as a new PR, as requested this time not from the main branch. I also added tests, although this was my first time using cypress, so I would be happy if someone could take a quick look at them. They pass with the new syntax and would fail if I would try them on some nonsense syntax like
x-transition.delay.500foo
, so I think they should successfully check for the new functionality.