We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
See the code snippet
Given this table design:
CREATE TABLE animal ( id SERIAL PRIMARY KEY ); CREATE TABLE cat ( id integer PRIMARY KEY REFERENCES animal );
An animal query should expose cat, a cat query should expose animal
animal
cat
An animal query exposes catById, a cat query exposes animalById
catById
animalById
The text was updated successfully, but these errors were encountered:
What happens if you rename cat.id to cat.animal_id?
cat.id
cat.animal_id
Sorry, something went wrong.
Ah, renaming to animal_id fixes it, but it does make the cat query cat(animalId: 10) slightly awkward.
animal_id
cat(animalId: 10)
Feel free to close the issue if you think it works as intended.
Nah, just making sure I understand the issue. I think this warrants improvement 👍 It's going to need special handling.
Successfully merging a pull request may close this issue.
Summary
See the code snippet
Steps to reproduce
Given this table design:
Expected results
An
animal
query should exposecat
, acat
query should exposeanimal
Actual results
An
animal
query exposescatById
, acat
query exposesanimalById
Additional context
Possible Solution
The text was updated successfully, but these errors were encountered: