Page 1 of 1

auto-complete token values and whitespace

Posted: Wed Oct 29, 2014 3:13 pm
by stefan.eissing
I have a XML document accompanied by a Relax NG schema that adds several tokens as choices for element values, as in

Code: Select all

  element e {
xsd:token "string1"
| xsd:token "string2"
| xsd:token "string11"
Autocompletion in Oxygen works, when the element is empty, like in:

Code: Select all


  <e>|</e>  <!-- offers all choices -->
<e>string1|</e> <!-- offers "string1" and "string11" -->
('|' is the cursor)

However my customer likes to use whitespace, which is fine with tokens, however the autocompletion no longer offers suggestions:

Code: Select all


  <e> |</e>  <!-- offers nothing -->
<e> str|</e> <!-- offers nothing -->
Anything I can do to make auto-complete work with leading/trailing whitespace for tokens? Adding patterns does not help, as those do not work in autocomplete at all. My understanding of "token" is that this whitespace should be ignored...

Re: auto-complete token values and whitespace

Posted: Mon Nov 03, 2014 6:15 pm
by adrian
Hello Stefan,

Your understanding is correct. Unfortunately this is yet another bug.
The content completion mechanism from Oxygen also considers the leading whitespaces as part of the item, even though for xsd:token they are not significant. This is the reason the items are filtered from the list of proposals (thus no suggestions are left).
I've submitted this to our issue tracking tool to be resolved in a future update. We will notify this thread when it is fixed.

I don't see a workaround for this issue.

Regards,
Adrian

Re: auto-complete token values and whitespace

Posted: Tue Nov 04, 2014 12:38 pm
by stefan.eissing
Thanks Adrian for opening a ticket on this.

Re: auto-complete token values and whitespace

Posted: Wed Jun 17, 2015 12:01 pm
by Radu
Hi,

Just to update this thread, the issue should be fixed in Oxygen 17.0.

Regards,
Radu