-
-
Notifications
You must be signed in to change notification settings - Fork 554
Order of canonical-data keys #1705
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think the order for virtually all of the existing canonical data is:
I'm fine with keeping this as is. Maybe we should add the "reimplements" key directly after the "uuid" key?
|
I'd like that because it keeps the unreadable part away from the rest |
@ErikSchierboom And {
"uuid": "25a8463d-560f-4a42-9be7-b79d00cd28a4",
"description": "64",
"property": "square",
"input": {
"square": 64
},
"expected": 9223372036854775808,
"scenarios": ["big-integers"]
} |
Ah, yes, forgot about that 🤦 Scenarios is basically metadata, so it would perhaps make sense to group it with the other metadata. Maybe:
or
I think I have a slight preference for the latter. |
I prefer later but not a hard preference. |
I prefer the latter too. |
Okay, lets go the following then:
|
Wouldn't this be a change to |
It would, but we're right in the middle of migrating configlet which could take a while. |
From @ee7 in #1703 (review)
Tasks:
The text was updated successfully, but these errors were encountered: