Skip to content
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

Order properties in a deterministic order in Details section #47

Open
3 tasks
FlorianJacta opened this issue Apr 21, 2023 · 0 comments
Open
3 tasks

Order properties in a deterministic order in Details section #47

FlorianJacta opened this issue Apr 21, 2023 · 0 comments
Labels
📈 Improvement Improvement of a feature. 🟩 Priority: Low Low priority and doesn't need to be rushed 🔒 Staff only Restricted to CC staff members

Comments

@FlorianJacta
Copy link
Member

Description
The order in the Details section is currently given from the TOML file. Sometimes, the Scope property is the first property; sometimes, it is the last depending on how the TOML file has been edited.

Properties seen in the Details section should have the same order. We could use the alphabetic order to do so. The goal is to have consistency across entity configurations.

Acceptance Criteria

  • Ensure new code is unit tested, and check code coverage is at least 90%
  • Propagate any change on the demos and run all of them to ensure there is no breaking change
  • Ensure any change is well documented
@FlorianJacta FlorianJacta added the 📈 Improvement Improvement of a feature. label Apr 21, 2023
@jrobinAV jrobinAV added the 🟩 Priority: Low Low priority and doesn't need to be rushed label Apr 5, 2024
@jrobinAV jrobinAV changed the title Order properties in alphabetic order in Details section Order properties in a deterministic order in Details section Apr 5, 2024
@jrobinAV jrobinAV added the 🔒 Staff only Restricted to CC staff members label Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📈 Improvement Improvement of a feature. 🟩 Priority: Low Low priority and doesn't need to be rushed 🔒 Staff only Restricted to CC staff members
Projects
None yet
Development

No branches or pull requests

2 participants