-
Notifications
You must be signed in to change notification settings - Fork 327
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
Yaml #168
Yaml #168
Conversation
Signed-off-by: Amndeep Singh Mann <[email protected]>
Signed-off-by: Amndeep Singh Mann <[email protected]>
Signed-off-by: Amndeep Singh Mann <[email protected]>
Signed-off-by: Amndeep Singh Mann <[email protected]>
This reverts commit d912dd0.
…n user_session, and then ran yamllint against those directories and fixed them (with the line length rule turned off) Signed-off-by: Amndeep Singh Mann <[email protected]>
Signed-off-by: Amndeep Singh Mann <[email protected]>
Signed-off-by: Amndeep Singh Mann <[email protected]>
…rate scripts, and current data. matching is non-strict so unexpected elements should be accepted. Signed-off-by: Amndeep Singh Mann <[email protected]>
Signed-off-by: Amndeep Singh Mann <[email protected]>
…be in the repo Signed-off-by: Amndeep Singh Mann <[email protected]>
Signed-off-by: Amndeep Singh Mann <[email protected]>
Resolves #151 tho would appreciate confirmation that the schema is created as intended since it is based off of the current repo, which may not reflect the intended state. Example: #169 complains about some CARs missing the 'coverage' field, which I had decided to mark as optional in the schema since I did not know about the intentionality of that field being missing, nor what to fill it with if it should actually be there. |
Workflow to lint the yaml based data via yamllint, certain business rules that we have to make our code work (ex. analytics ids should be the same as their filename), and against schemas.