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
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.
The text was updated successfully, but these errors were encountered:
Grokzen
changed the title
Create different versions of validation rules
Create different implementations of kwalify syntax
Mar 22, 2016
Grokzen
changed the title
Create different implementations of kwalify syntax
Create different implementations/generations of kwalify syntax
Mar 22, 2016
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 andmodern
orstandard
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 thestrict
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.The text was updated successfully, but these errors were encountered: