Skip to content

Conversation

@samvrlewis
Copy link
Contributor

Description

I was surprised that these files weren't auto-generated, but listing
this as an extra step will hopefully avoid confusion for developers
adding new message groups in the future.

API compatibility

Does this change introduce a API compatibility risk?

No

I was surprised that these files weren't auto-generated, but listing
this as an extra step will hopefully avoid confusion for developers
adding new message groups in the future.
@samvrlewis samvrlewis requested a review from a team as a code owner July 1, 2022 04:55
@samvrlewis
Copy link
Contributor Author

IMO this should probably be part of the code generation step, as it's really easy to forget adding this (and seemingly only caught if you add message specific tests - so luckily I did that!), so I added a couple of bugs to track: https://swift-nav.atlassian.net/browse/DEVINFRA-804?jql=issueKey%20in%20(DEVINFRA-803%2CDEVINFRA-804)

@samvrlewis samvrlewis merged commit c9deea6 into staging Jul 1, 2022
@samvrlewis samvrlewis deleted the slewis/new-group-instructions branch July 1, 2022 05:21
samvrlewis added a commit that referenced this pull request Jul 6, 2022
I was surprised that these files weren't auto-generated, but listing
this as an extra step will hopefully avoid confusion for developers
adding new message groups in the future.
samvrlewis added a commit that referenced this pull request Jul 6, 2022
I was surprised that these files weren't auto-generated, but listing
this as an extra step will hopefully avoid confusion for developers
adding new message groups in the future.
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.

3 participants