Add documentation about using guards for map fields #11913
Merged
Conversation
This file contains hidden or 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
josevalim
reviewed
Jun 8, 2022
| # ... | ||
| :ok | ||
| end | ||
| ``` |
There was a problem hiding this comment.
Nice catch!
I am not sure if this deserves its own section but we can add an entry to the list in ## Guards. WDYT?
There was a problem hiding this comment.
Sounds good, I've added an entry there 👌
whatyouhide
approved these changes
Jun 9, 2022
josevalim
reviewed
Jun 9, 2022
|
💚 💙 💜 💛 ❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Hi there! 👋
This commit adds a little documentation about being able to use
map.fieldinside guards.I couldn't find in the docs any mention, thought it would be good to write there it's a possibility, what do you think?
Thanks!