-
Notifications
You must be signed in to change notification settings - Fork 4
Request Field Casing #10
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
Open
chrisjainsley
wants to merge
8
commits into
nkovacic:develop
Choose a base branch
from
chrisjainsley:bugfix/request-field-casing
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Request Field Casing #10
chrisjainsley
wants to merge
8
commits into
nkovacic:develop
from
chrisjainsley:bugfix/request-field-casing
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merge to master
This commit introduces significant improvements to how JSON property names are managed and serialized across the application. Key changes include the addition of the Newtonsoft.Json namespace to enhance JSON serialization capabilities. The `JsonProperty` attribute is now utilized in `Listing.cs` to customize the serialization name of the `Place` property to `"placeCoordinates"`, ensuring alignment with external API or data storage formats. Furthermore, `AzureSearchMapping.cs` has been updated to leverage the `JsonPropertyAttribute` for more accurate and flexible property name mapping. This is complemented by the refactoring of `AzureSearchFieldsExpressionVisitor.cs`, which now uses the `NameHelper.GetMemberName` method for consistent field naming, abstracting away direct name manipulation. The introduction of the `NameHelper` utility class centralizes the logic for resolving member names, supporting both explicit naming through `JsonProperty` attributes and default camel casing. This utility is also employed in `MemberProjectionExpressionVisitor.cs` to maintain naming consistency across the application. Overall, these changes significantly enhance the flexibility and consistency of JSON property naming within the application, promoting better maintainability and code reuse.
nkovacic
reviewed
Jul 24, 2024
Owner
nkovacic
left a comment
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.
Seeing only formatting issues, otherwise great 👍.
Author
|
@nkovacic, could we merge and release this? Let me know if there is anything I can do to help. |
Author
|
Bumping this up again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added the ability to use the json.net's Json Property Attribute to map to the correct Azure search index fields.
#9