Better XPath suggestions
Are you missing a feature? Request its implementation here.
-
- Posts: 7
- Joined: Wed Jan 11, 2017 12:26 pm
Better XPath suggestions
Hi,
I've noticed that the context-aware XPath suggestions fail in following situations:
- when adding boolean operators 'and' or 'or' in the expression, no context-specific suggestions are given after it. E.g. -> in this case, the auto-completion stops working after 'or', even though it should behave as if it were the beginning of the expression.
- when you have a variable that contains a nodeset, no context-specific suggestions are given when referring to that variable. E.g. with this input: and this XSL: -> 'subNode' should be suggested after the slash. Obviously this only works when the variable is a nodeset.
This would be very helpful when dealing with more complicated XPath suggestions.
Thanks for considering this.
I've noticed that the context-aware XPath suggestions fail in following situations:
- when adding boolean operators 'and' or 'or' in the expression, no context-specific suggestions are given after it. E.g.
Code: Select all
<xsl:if test="node/subnode or..."/>
- when you have a variable that contains a nodeset, no context-specific suggestions are given when referring to that variable. E.g. with this input:
Code: Select all
<node><subnode/></node>
Code: Select all
<xsl:variable name="aNode" select="node"/>
<xsl:value-of select="$aNode/..."/>
This would be very helpful when dealing with more complicated XPath suggestions.
Thanks for considering this.
-
- Posts: 9434
- Joined: Fri Jul 09, 2004 5:18 pm
Re: Better XPath suggestions
Hi,
Thanks for the feedback. So:
Regards,
Radu
Thanks for the feedback. So:
Indeed if the content completion from the set of XML elements worked before the "or"/"and" it should have also worked after it, I will add an issue on our side and we'll try to make this work in a future version. I will update this forum thread when we do.when adding boolean operators 'and' or 'or' in the expression, no context-specific suggestions are given after it
I understand but it's quite impossible to make this work. The value of the variable may be computed and determined at runtime and we do not run the XSLT transformation in order to give you suggestions.when you have a variable that contains a nodeset, no context-specific suggestions are given when referring to that variable.
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service