-
Notifications
You must be signed in to change notification settings - Fork 175
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
Added rule: "Do you check your API serialisation format?" #8549
Added rule: "Do you check your API serialisation format?" #8549
Conversation
Howzit @christoment, This PR has been here a while. Did you know you should avoid merge debt?
Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
The .NET Framework story is a bit less trivial because you have Katana, Owin, ASP.NET, ASP.NET Core and probably more. I remember some combination gave you camelCase by default.
I think, it's good as it is in order to not complicate it any further. 😄 (and that it slowly drifts into archive)
Things I found during migrating TimePro to .NET 8.
Added rule - Do you check your API serialisation format?