-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[#10939] Enable addLocationInformation in DefaultModelXmlFactory base on InputLocationFormatter presence #10940
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
Giovds
wants to merge
5
commits into
apache:master
Choose a base branch
from
infosupport:issue-10939-location-tracking-depending-on-formatter
base: master
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
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
acbc713
[#10939] Enable addLocationInformation in DefaultModelXmlFactory base…
Giovds 4773734
[#10939] Replace assertThat with assertEquals in DefaultModelXmlFacto…
Giovds d9a3399
[#10939] Refactor location tracking logic to depend on stringFormatte…
Giovds d521474
[#10939] Add non-formatter constructor to reflect original behaviour
Giovds db06137
[#10939] Apply Spotless
Giovds 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
Oops, something went wrong.
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.
maybe use an else block for this; what's the default?
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.
The
MavenStaxWriter
is initialized withtrue
therefore I explicitly set it tofalse
. I personally prefer to keep nesting brackets to a minimum, as this makes it less verbose and easier to understand what's happening. The result would be the same?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.
In that case, no need to set it to true below. Use an else block to set it to false
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.
That would make it depend on the implementation of the
MavenStaxWriter
. If it changes the default this will affect our class.I was thinking the same as @gnodet:
If we use the proposed solution of moving this behaviour to the
MavenStaxWriter
this might solve both the need to set the value, and other XML factory implementations.This is a generic generated class (through
writer-stax.vm
), so allZZZStaxWriter
classes (which are about 8 classes) will use this behaviour from then on. I'm not entirely sure about that change, but probably will be the better option as it will solve the issues for otherDefaultZZZXmlFactory
classes as well that use one of theZZZStaxWriter
's.