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

[Bug]: converter does not warn if variadic concept name is invalid #563

Open
rettigl opened this issue Feb 26, 2025 · 0 comments
Open

[Bug]: converter does not warn if variadic concept name is invalid #563

rettigl opened this issue Feb 26, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@rettigl
Copy link
Collaborator

rettigl commented Feb 26, 2025

Contact Details

No response

What happened?

If the template dictionary contains an instance of a variadic name, e.g. ENTRY[entry], and that variadic concept does not match a concept in the application definition, no warning is raised, and the respective group is written without proper NXclass attribute.

Example:

  • With "entry/USER[user]" I get:
    Image
  • With "entry/USE[user]" I get:
    Image

Neither produces a warning.

Relevant log output

@rettigl rettigl added the bug Something isn't working label Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant