Add lutro.featureflags table, for use in determining lutro build capabilities #266
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is primarily intended for use in internal dev and unit test development. A practical application is that it can be used (soon) to detect whether the lutro build supports the transform rendering feature, and then alter lua graphics test behavior accordingly.
This change was inspired by work done in PR #215 which adds Transform and Scaling features.
I've selected the name
lutro.featureflags
instead oflutro.config
used in PR #215 to improve clarity and avoid ambiguity with various other types of configurations (namely ones coming from data-driven or runtime sources such as ini files, for which the term 'config' is probably more readily associated).test output
Running the unit tests produces this output: