-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Ensure metadata location when created from xml element with known location #8599
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
Merged
Merged
Changes from 3 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
226514e
Populate location of attributes/elements created from other node with…
JanKrivanek 5ab53ea
Handle nulls gracefully
JanKrivanek 9ad1805
Fix API breaking change
JanKrivanek 438d48b
Replace setter with AsyncLocal
JanKrivanek 60fdf2e
Merge remote-tracking branch 'upstream/main' into proto-metadata-loc
JanKrivanek c03fd0f
Remove temporary hack
JanKrivanek c912e28
Add missing comment
JanKrivanek d87a96f
Add unit tests
JanKrivanek File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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.
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.
nit: I wonder if there's a slightly more elegant way of setting location for newly created elements than adding a Location setter. If you passed the location to
ProjectRootElement.CreateElementwhich in turn would pass it to a new overload ofXmlDocumentWithLocation.CreateElement, you could set its_readerfield for the duration of the base call, similar to whatLoaddoes. Note that_readeris of typeIXmlLineInfo, so not necessarily an XML reader. Or you could introduce a new field (_currentLocation?) , which would then even avoid boxing.Overall, I would find it nicer to leave the
*WithLocationclasses concerned with setting location without leaking the setter like this. What do you think?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.
Thanks for looking into this! Great suggestion!
I was as well trying to see if I can just extend the creation and avoid subsequent mutation.
The problem that stopped me and let me to current code is that the
XmlDocumentWithLocationextendsXmlDocumentand our overridenCreateElementis not being called directy, but via aXmlDocumentfunction that inside calls internal helper function:So we'd need to duplicate some of that internal
XmlDocumentfunctionality (and maintain it going forward).Not sure which is the lesser evil (allowing mutations vs duplicating
XmlDocumentcode) - I arbitrarily decided for openng for mutation.What do you think about this?
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.
Great thanks for offline discussion and tips! - I ended up passing the info via
AsyncLocalfiled.