adds content for many-to-many relationships (close #399) #807
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
rikinsk-zz
approved these changes
Oct 18, 2018
|
Review app https://hge-ci-pull-807.herokuapp.com is deleted |
Deploying with
|
| Latest commit: |
9318cb2
|
| Status: | 🚫 Build failed. |
This was referenced Dec 19, 2023
This was referenced Mar 22, 2024
hasura-bot
pushed a commit
that referenced
this pull request
Jul 9, 2024
<!-- The PR description should answer 2 (maybe 3) important questions: --> ### What We pass around a lot of `BTreeMap` and `IndexMap` types. This has two problems: a) everytime we change the items inside, we have to manually update lots of call sites b) we can't attach useful behaviour to it <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> ### How This adds some wrappers around `object_types`, and adds a `.get()` function with a useful default error. This error only contains the missing `type_name`, so the idea is that it would be wrapped in another error that would provide more context. The hope is that we can get away from one giant error enum, and instead have a set of smaller error types that live along each resolving stage. In isolation this PR isn't very interesting, as it's a tiny drop in the ocean, so really it's here to say, "is this a thing we vaguely like?" <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 804a703d7155ce5b929937689d5649c6571357b0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds content in docs for modelling/creating many-to-many relationships.
What component does this PR affect?
Requires changes from other components? If yes, please mark the components:
Related Issue
#399
Solution and Design
The treatment is slightly different from the outline specified in #399 because it's more of a process than creating array/object relationships which are options in the console. So, it's been accorded a separate section which is referred to in the introductory section.
Type
Checklist: