Default display name splitting should handle properties containing periods
See original GitHub issueRuleFor(x => x.Address.Line1)
generates a display name of “Address. Line1” instead of “Address Line1”.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Name computers, domains, sites, and OUs - Windows Server
Period characters are allowed only when they're used to delimit the components of domain style names. Windows domain name system (DNS) supports ...
Read more >A Guide on Split () Function in Python
Here, you can see the variable str is declared with a string of different subject names. The Split function takes whitespace (“ ”)...
Read more >about Split - PowerShell
The Split operator splits one or more strings into substrings. You can change the following elements of the Split operation: Delimiter.
Read more >How To Handle Async Data Loading, Lazy Loading, and ...
This tutorial will explain how to avoid this with a special Hook called useEffect , which will run functions only when specific data...
Read more >4 Formatting Query Results
SQL*Plus uses column or expression names as default column headings when displaying query results. Column names are often short and cryptic, however, ...
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 FreeTop 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
Top GitHub Comments
Merged for 10.0
Also this is extremely low priority as typically you’d specify an overridden display name by calling WithName in this scenario anyway.
If you want to dive in then the documentation updates would be higher priority as I need to get those done before I can release 9.0