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

reason tokens for why an API is public/protected #355

Open
luxe opened this issue Oct 18, 2018 · 1 comment
Open

reason tokens for why an API is public/protected #355

luxe opened this issue Oct 18, 2018 · 1 comment

Comments

@luxe
Copy link
Owner

luxe commented Oct 18, 2018

sometimes there is functionality that someone wants, but it is not accessible(and not testable) since it is private. Maybe we should have a language token for ["why this is public"] and ["why this is private"].
Something to think about. We wouldn't want to say "this is called by this internally which is why its private". But we may have reasons that something is private... In the event that we may consider changing it, without affecting public interfaces. We might want to provide a note for users to prevent them or have them think about the ramifications of moving an interface from private to public.

@luxe
Copy link
Owner Author

luxe commented Jun 11, 2021

probably everything should allow a reason token. Its a meta property of any user chosen value. This should probably be added automatically, and not put into the actual concept.dat

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

1 participant