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.
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
Lickem22 user management #455
base: main
Are you sure you want to change the base?
Lickem22 user management #455
Changes from 5 commits
61fca47
4ce441c
0f11960
cbb01e3
256bbe0
91af728
685d15c
1c4eb84
d5cd837
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Large diffs are not rendered by default.
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.
Should
UserModal
be underapp/components
since it seems to be used in multiple places?The coupling between low-level components (
app/login/components/RegisterModal
->user-management/components/UserCreateModal
) seems like a bad idea.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.
It's one of things that leads to code bases where if you change one thing, you have to now change a bunch of unrelated components
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.
if not using
event
, let's make it_
.Also, why is
reason
optional? I don't think it should be?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.
I see why you are making it optional. It's to meet the type requirement for
onClose
onUserModalProps
.Maybe that should be a different signature. I'll comment there as well.
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.
Same 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.
Why is
UserBody
type needed foruser
here? Is it for google login user and the password gets set as blank?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.
I have a "Parent" modal
UserModal
that can be done to register the first user, register all users and edit users. Since it can do both registering and editing it needs to support UserBodyPassword and UserBody, If I do :(user: UserBodyPassword)
I am going to get a syntax error.