-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Migrate group_domain_models
package null safety
#495
Conversation
Visit the preview URL for this PR (updated for commit b20b368): https://sharezone-test--pr495-migrate-group-domain-xb47pm61.web.app (expires Thu, 17 Aug 2023 00:26:13 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 4cb3ae61e1e018abfd9841fd3239f5b49ccc034b |
required String id, | ||
required Map<String, dynamic> data, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit (maybe for some other PR): For some classes data
is positional and id
is named and for example here both is named. We should decide on one of both for all cases.
default: | ||
return 'Einstellung konnte nicht gefunden werden'; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couldn't we only use both cases in the switch and put the fallback as a separate return after it so that if a new WritePermission
case is introduced we get a warning here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nilsreichardt Do you want to look at it again or should I go ahead and merge?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Closes #192