Skip to content
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

p:option @values error can't be a static error #823

Closed
ndw opened this issue Jun 28, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@ndw
Copy link
Contributor

commented Jun 28, 2019

Currently, the description of p:option says:

values

A list of acceptable values may be specified in the values attribute. If specified, the value of the values attribute must be a list of atomic values expressed as an XPath sequence, for example: ('one', 'two', 'three'). It is a static error (err:XS0101) if the values list is not an XPath sequence of atomic values.

I don't believe that can be a static error in the general case.

@xml-project

This comment has been minimized.

Copy link
Contributor

commented Jun 29, 2019

Hhm, thinking of a situation, where a option declaration is not parsed statically. Could you give us an example, where @values is not analysed statically?

@ndw

This comment has been minimized.

Copy link
Contributor Author

commented Jun 29, 2019

Nevermind. I completely misread that as the error to raise if the supplied value wasn't a member of the list. #braincramp

@ndw ndw closed this Jun 29, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.