Create different implementations/generations of kwalify syntax
- Dominant language
- Python
- Stars
- 297
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Description
Currently there is some problems with that the syntax definition just grows as more and more features is added on top of the original kwalify syntax.
The long term suggestion is to make 2 different syntax schemas where one is a `strict` version that just implements the syntax that the original kwalify supported. Then there should be a newer and more modern version of the syntax that has all the backwards compatible kwalify syntax but also includes the new rules and syntax.
Suggested terms could be `strict` for the original kwalify and `modern` or `standard` for the second iteration.
The suggestion is to make the `modern` variant the default so that no changes will have to be imposed on people who currently uses all the new features. Then there will be added an option to use the `strict` version for people that requires it.
This is a long term plan and will probably make/bump the version to `2.0.0` when implemented.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.