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.

Sign up for GitHub

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

Jump to bottom

Is exists_one getting renamed to existsOne? #424

Open
hudlow opened this issue Dec 17, 2024 · 2 comments
Open

Is exists_one getting renamed to existsOne? #424

hudlow opened this issue Dec 17, 2024 · 2 comments

Comments

@hudlow
Copy link
Contributor

hudlow commented Dec 17, 2024

It seems so in this PR, but I can find no evidence of a corresponding change to the spec.
@TristonianJones
Copy link
Collaborator

You're very observant, thanks for bringing this up. I feel like exists_one was an accident since function syntax should be camelCase rather than snake_case. We'll retain support for both, though I will likely shift the documentation to existsOne once all implementations support the new macro name.

@hudlow
Copy link
Contributor Author

hudlow commented Jan 7, 2025

Would it be feasible to have a bleeding edge branch of the language spec where these things are specified ahead of code changes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@TristonianJones @hudlow