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.
Feature - Allow Users to provide a browser config for Autoprefix
koala-config.json
project files to be used and take precedence over GUI settingskoala-config.json
files for LESS and SASS for project templates@oklai I have a question involving the user config json and the priority - Should the users project settings json config take priority over the settings from the GUI? or the other way around? Currently this is set up so that if a project config file exists, that should be used over the settings in the GUI, can easily be swapped around but this looks to be the priority for all other settings (i.e ignores). Thanks!