Update plan.md to clarify many-to-many #2125
Merged
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
There are multiple GH issues tracking the various components of many-to-many. Previously, only one of them was mentioned here. I have added the rest. Please feel free to adjust/edit as you see fit. (I couldn't find an issue for the configuration sugar) I have also added additional text to clarify which issues are planned and which are only stretch goals.
|
@vslee I like the idea here! Not merging immediately because I want to think about the exact language and formatting, since this is an important doc. |
|
Yes of course. These changes make the style of that section different than the others, so they likely need to be revised to conform better. |
|
This now merged. Thanks! |
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.
There are multiple GH issues tracking the various components of many-to-many. Previously, only one of them was mentioned here. I have added the rest. Please feel free to adjust/edit as you see fit. (I couldn't find an issue for the configuration sugar)
I have also added additional text to clarify which issues are planned and which are only stretch goals.