You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the suggestion! This still seems reasonable to me. As a bit of context we tend to have the LST elements merely represent the underlying structure, while we use higher level constructs like visitors and traits to make it easier to manipulate the underlying elements. That then also means there's less of a need to evolve the LST elements, which helps backwards compatibility with our serialization. Not sure how that work out exactly in this case, but perhaps it's good to explore two or more options briefly.
What problem are you trying to solve?
I am reading information from a
Xml.Tag
via theXmlIsoVisitor.visitTag
method. I have to read the value of a specific attribute.Right now, this is harder than it needs to be.
Describe the solution you'd like
I'd like to see a convenience method that does something similar to
getAttributeValue
. Is this something you'd consider?Have you considered any alternatives or workarounds?
Yes, see method above.
Additional context
N/A
Are you interested in [contributing this feature to OpenRewrite]
Yes
The text was updated successfully, but these errors were encountered: