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

Machine-readable way to define a namespace prefix #3

Open
merkys opened this issue Jun 11, 2024 · 2 comments
Open

Machine-readable way to define a namespace prefix #3

merkys opened this issue Jun 11, 2024 · 2 comments

Comments

@merkys
Copy link
Member

merkys commented Jun 11, 2024

Currently there is no machine-readable way to define the namespace prefix used in the namespace repository. It might not be needed at all, and possibly can be given in some external link aggregator, however, I can think of at least one use: validation of property names (they should start with a common suffix).

@ml-evs
Copy link
Member

ml-evs commented Jun 11, 2024

My understanding was that it is generated by the folder hierarchy, so that it does not need to be explicitly listed in each property definition itself (which could be error prone) (cf. the other issue on the stability repo)

@merkys
Copy link
Member Author

merkys commented Jun 11, 2024

Good point, but I do not see where from the prefix could be taken. One possibility is to look at the (supposedly) single file under src/$VERSION/standards/, but it would be nice to have a clarification about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants