Open ln4r3n opened 3 months ago
Right now all the changes that have been made have been backwards compatible. Once we add variables to a new spec, those variables in the builder will default to some base0x
value if it's not provided. I don't think adding a more strict version system like you're suggesting is a bad idea if we were to start adding breaking changes. Making the decision to add breaking changes is quite a big step though and it might be easier to create a new scheme spec if we were to do that. What do you think @belak?
For future proofing the project i think it's necessary to add
version
(for possible color changes) andspec
to schemes files.Also I propose another metafile for templates (parsed by builders):
tinted-template.yaml
with contents such as (my example is the official vim plugin),this needs to be present in the root of the template repo:With these changes the user and builder both can easly check for compatibility, supported systems, etc.