unoproj: support lowerCamelCase property names (beta-3.0) #466
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We want to accept property names written in lowerCamelCase, in unoproj- files, unoconfig-files, and uxl-files; to better match JavaScript and modern .NET, and best practices. In other words, users can now chose if they want to keep their existing UpperCamelCase style in project files or switch to lowerCamelCase, which is recommended for new projects built on version 3.0. We will update existing project and config files in upcoming patches, so this comes with functional changes to begin with, making sure both styles are tested.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We want to accept property names written in lowerCamelCase, in unoproj- files, unoconfig-files, and uxl-files; to better match JavaScript and modern .NET, and best practices.
In other words, users can now chose if they want to keep their existing UpperCamelCase style in project files or switch to lowerCamelCase, which is recommended for new projects built on version 3.0.
We will update existing project and config files in upcoming patches, so this comes with functional changes to begin with, making sure both styles are tested.