Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use CamlCase for Property names, add support for default values #93

Merged

Conversation

hoffmann-stefan
Copy link
Member

@hoffmann-stefan hoffmann-stefan commented Jun 15, 2022

Some small PR that implements #91.
I chose CamelCase as there is currently the most preferred alternative in that issue (though there are not many votes).

Additionally added support for default values in ros interfaces, but if you like I could extract them to a separate PR.

If we want't to make the old names still work but obsolete we can use something like this: https://gist.github.com/hoffmann-stefan/0aa0809ac0b511e837ca761a438b044a

@hoffmann-stefan
Copy link
Member Author

Merging this togeter with #90 as both significantly break the API of this library. Users can update this now in one go.

@hoffmann-stefan hoffmann-stefan merged commit 68c51e6 into ros2-dotnet:master Apr 22, 2023
3 checks passed
@hoffmann-stefan hoffmann-stefan deleted the idl-defaults-and-naming branch April 22, 2023 07:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Reconsider property naming convention in generated messages
1 participant