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
As part of recipe quality assurance (QA) we will likely have various standards for how recipes should be formatted. This might mean capitalisation in certain places or ending method steps with a full stop. This validation could be added as a step to ingestion, after JSON ingestion and before loading into the database.
Simplest implementation could be a single function that takes a recipe and either:
Does nothing
Prints a warning
Fails the build
Depending on the severity of the issue.
The text was updated successfully, but these errors were encountered:
We have since moved from JSON recipes to Scala, which greatly reduces the possibility of errors. Further validation could be added using refined types: https://github.com/fthomas/refined
As part of recipe quality assurance (QA) we will likely have various standards for how recipes should be formatted. This might mean capitalisation in certain places or ending method steps with a full stop. This validation could be added as a step to ingestion, after JSON ingestion and before loading into the database.
Simplest implementation could be a single function that takes a recipe and either:
Depending on the severity of the issue.
The text was updated successfully, but these errors were encountered: