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
Our rules are currently defined and presented as a Markdown table in the ecoCode repository. Although this centralizes the rules, they are still too hidden and poorly presented in an unclear table. What's more, we have to update it manually! So many possible inconsistencies.
To showcase all our painstaking work and make the rules available to as many people as possible, we need to present them in a different form. That's where a new section on the site comes in! 🔥
Important features are:
List of all rules in the main repository (can be filtered/sorted by technologies, severity)
Detail of all rules with descriptions, infos and references
Automatically updated to avoid inconsistencies
Let's get down to a bit of architecture!
This schema briefly presents the idea and how the repositories will communicate with each other (in french).
This EPIC can be splitted into small tasks:
1. Check the technical feasibility of integration with the tool
2. Web and mobile design
3. Create the automated task to build rule metadatas
4. Website integration
The text was updated successfully, but these errors were encountered:
Our rules are currently defined and presented as a Markdown table in the ecoCode repository. Although this centralizes the rules, they are still too hidden and poorly presented in an unclear table. What's more, we have to update it manually! So many possible inconsistencies.
To showcase all our painstaking work and make the rules available to as many people as possible, we need to present them in a different form. That's where a new section on the site comes in! 🔥
Important features are:
Let's get down to a bit of architecture!
This schema briefly presents the idea and how the repositories will communicate with each other (in french).
This EPIC can be splitted into small tasks:
The text was updated successfully, but these errors were encountered: