NEST 6.0 GA: JsonProperty attribute support, Rename gone?
See original GitHub issueWe have some DTOs that we’ve previously been able to share among our middle tier C# models and the models we use for ES. I’ve seen ES 5.x documentation which shows that JsonProperty
is allowed but w/ the internalization of Newtonsoft (or whatever parser you’ve chosen), I’ve discovered that I have to use Rename
or Text
on all my models which would be fine except where I want directly share them as I explained above. Should JsonProperty
still be supported as before in NEST 6.0? I just discovered this because, for some of our indexes, we use strict
mappings. Anyway, the DTOs are in a place where I’d prefer not to expose the Nest library.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
How can I rename sub-properties of ...
I have implemented that stuff for first-level object properties when serializing using custom ContractResolver like here:
Read more >Elasticsearch.Net and NEST - Breaking changes
This lists all the binary breaking changes in NEST from 5.x (last commit in 5.x at time of 6.0.0 GA release) to 6.x...
Read more >JsonPropertyAttribute name
JsonPropertyAttribute name. This sample uses JsonPropertyAttribute to change the names of properties when they are serialized to JSON.
Read more >Cumulative Changes from Net Express to ...
This provides edit, compile and debug support for Visual COBOL and Enterprise Developer users in Visual Studio Code. Note: The new Micro Focus ......
Read more >Cumulative Changes from Server Express to ...
The version of Visual COBOL in which the change was introduced,. • A link to more information. ... addition of the JSON property...
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
@jonyadamit yes that is correct.
The
PropertyNameAttribute
helped a lot for me. Thanks @russcam