Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Setup Guidelines for Propertynames (PascalCase instead of CamelCase)
See original GitHub issueCurrently some of our components like a <AntButton/> uses camelcase for it’s property names.
We should use PascalCase see <AntBadge/> or <AntAlert/>
Todo
- Add Linter #32
- Update all Properties for all components.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
c# - Proper Property Naming
Standard way is Pascal Case for Properties and camel case with an underscore for fields. public string Name { get; } private string...
Read more >How to customize property names and values with System. ...
Customize individual property names; Convert all property names to camel case; Implement a custom property naming policy; Convert dictionary ...
Read more >New Rule: Property Name's Should be PascalCase · Issue ...
We have settled on a standard of property names are in CamelCase. Is this something that fits within the scheme of constraints you...
Read more >How to enable case-insensitive property name matching ...
Here's example JSON with camel case property names. It can be deserialized into the following type that has Pascal case property names.
Read more >Serializing a PascalCase Newtonsoft.Json JObject to ...
In this post I describe one of the quirks of serializing a JSON.NET JObject, and show how to get camelCase names from a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
fix in #82
Ok, let’s follow the convention. I think we need to add a lint to check PRs.