You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 20, 2024. It is now read-only.
If an object has both the key/value then we'd also ignore the length of the value and only use key.length.
Example:
cy.task('record:fast_visit_spec',{url,
percentiles,foo: 'a really long string that'slongerthanthefollowingvalue', browser: Cypress.config('browser').name
})
When order matters
If order matters, such as when using the spread operator syntax, then avoid sorting...
Example:
constobj={
...veryLongObject,
...shortObj,
foo,// this does not get sorted above the others...
quux,// but this gets sorted
lorem,// and this gets sorted}
The text was updated successfully, but these errors were encountered:
I have strong feelings about this. I would prefer alphabetical
cy.task('record:fast_visit_spec',{browser: Cypress.config('browser').name,foo: 'a really long string that'slongerthanthefollowingvalue',
percentiles,
url
})
Given an object looking like this...
When order does not matter
Could we autosort the keys to be grouped into two groups...
shorthand
propertiesAnd then subsequently short by the length of the key for both groups?
So it would subsequently restructure the object to look like...
If an object has both the
key/value
then we'd also ignore the length of the value and only usekey.length
.Example:
When order matters
If order matters, such as when using the
spread
operator syntax, then avoid sorting...Example:
The text was updated successfully, but these errors were encountered: