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

Restrict conflicting names and reserved names #17

Open
inkeliz opened this issue Jul 31, 2022 · 0 comments · May be fixed by #87
Open

Restrict conflicting names and reserved names #17

inkeliz opened this issue Jul 31, 2022 · 0 comments · May be fixed by #87

Comments

@inkeliz
Copy link
Owner

inkeliz commented Jul 31, 2022

Currently, the only limitation related to naming is:

  • Must be A-Z
  • Must not start with number

That may cause issues depending on the language used, since some words can be reserved by the language or internally by karmem itself (such as SizeOf() function).

The goal is to have a list of words that can't be used as name.

@inkeliz inkeliz moved this to Future in Karmem: Roadmap Aug 23, 2022
@inkeliz inkeliz moved this from Future to Stage 3: Generator 1 in Karmem: Roadmap Aug 23, 2022
inkeliz added a commit that referenced this issue Sep 1, 2022
Now, Karmem will report with "Warnings" with the schema contains
potential conflicts with the names or uses reserved names.

It's possible to avoid it using `-s`.

Fixes #17
inkeliz added a commit that referenced this issue Sep 2, 2022
Now, Karmem will report with "Warnings" with the schema contains
potential conflicts with the names or uses reserved names.

It's possible to avoid it using `-s`.

Fixes #17
inkeliz added a commit that referenced this issue Sep 2, 2022
Now, Karmem will report with "Warnings" with the schema contains
potential conflicts with the names or uses reserved names.

It's possible to avoid it using `-s`.

Fixes #17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Stage 3: Generator A
Development

Successfully merging a pull request may close this issue.

1 participant