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

Source Schema Chapter #30

Open
wants to merge 45 commits into
base: main
Choose a base branch
from
Open

Source Schema Chapter #30

wants to merge 45 commits into from

Conversation

michaelstaib
Copy link
Member

@michaelstaib michaelstaib commented Apr 11, 2024

This PR renames the @entityReslolver to @lookup and introduces the agreed characteristics to the specification.

TODOs:

  • Semantics of lookups vs patches RFC document (Michael).

Copy link
Member

@benjie benjie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's more missing colons I've missed.

spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved
spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved
spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved
spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved
spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved
spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved
spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved
spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved
spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved
spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved
spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved
spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved
spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved
spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved
spec/Section 2 -- Source Schema.md Outdated Show resolved Hide resolved

```graphql counter-example
type Query {
product(id: ID!, categoryId: Int): Product @lookup

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as discussed during last meeting I believe this is actually valid?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes ... I am gonna rewrite this part.

```

Nested lookups must imediately follow the parent lookup and cannot be nested
with fields inbetween.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe we agreed that inbetween fields are allowed only if they don't have any arguments

michaelstaib and others added 8 commits August 1, 2024 17:13
Co-authored-by: Glen <glen.84@gmail.com>
Co-authored-by: Glen <glen.84@gmail.com>
Co-authored-by: Glen <glen.84@gmail.com>
Co-authored-by: Glen <glen.84@gmail.com>
Co-authored-by: Glen <glen.84@gmail.com>
Co-authored-by: Glen <glen.84@gmail.com>
Co-authored-by: Glen <glen.84@gmail.com>
@michaelstaib michaelstaib changed the title Introduce Lookup Directive. Source Schema Chapter Aug 1, 2024
@michaelstaib michaelstaib marked this pull request as ready for review October 3, 2024 13:30
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

Successfully merging this pull request may close these issues.

6 participants