-
Notifications
You must be signed in to change notification settings - Fork 19
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
Change: confirm button text to create motion #3528
Conversation
@Julianahlk To request a review from everyone, you can use the |
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.
Works great, nice one @Julianahlk!! Congrats on your first PR 🥇
Thanks @arrenv I will use that tag next time. Happy it works as intended. Thanks for reviewing it! |
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.
Great work for your first PR. There are 2 things to correct:
- I think that you forgot the
NetworkContractUpgradeDialog
- In the create motion version of the button the text is not centred as per below. It's a tricky thing to notice and I paid attention because I had to update the button styles in another PR to fix this.
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.
Nice PR! I presume the dialogs that have not been changed (e.g. ManageWhitelistDialogForm
(Manage Address Book)) haven't been changed because they don't require a motion to be submitted? Or is every dialog supposed to have this "Create Motion" text?
@chinins Oh I nice, thanks for catching that one I missed. |
You are correct, the "missing" dialogs do not create a Motion, as they are basically cheating behind the scene and do not call a contract function, in the same way as the others do |
For this you'll have to add local styles that overwrite the |
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.
Other than what Olga found, I'm good with this.
I'm pre-approving, but do please address Olga's concerns before merging
On it @rdig ! Thank you for the brief explanation. |
I switched the width property to be minWidth so the Create Motion/Confirm button could expand to fit any future size text (localized text). I am not sure if this what you were looking for but I think it is more future proof as the buttons can handle longer text if necessary. Let me know what you think. |
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.
loading={isSubmitting} | ||
disabled={!isValid || inputDisabled} | ||
style={{ width: styles.wideButton }} | ||
style={{ minWidth: styles.wideButton }} |
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.
We usually prefer to add this via css styles not via JS.
You can do the same, by overwriting the button min-width
in the styles file
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.
@rdig So my goal was to remove the width style and replace it with minWidth. Are you saying that having the width style in the tsx file wasnt the best way to do it to begin with?
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.
Exactly. But now that I'm thinking more about this, in order to expedite this PR, leave it like it is for now.
Let's just fix your branch tommorow, then you can merge it
{isUserReputationLoading ? ( | ||
<SpinnerLoader | ||
appearance={{ | ||
theme: 'grey', | ||
size: 'small', | ||
}} | ||
/> |
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.
How did this changes end up in here ? These are not related to your branch.
Did you cherry-pick them from somewhere? If so, why ?
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.
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.
Yeah, some rebase / merge screwed up your branch. We'll fix it tommorow.
@rdig Regarding the bad merge. Im not sure why this happened this time because I did try to use, |
7363973
to
6b07a18
Compare
@chinins I implemented the changes you suggested and solved my merge conflicts with Raul yesterday. Can you please take a look at this PR again whenever you have a chance? Thank you! |
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.
All good - nice work!
Thank you! |
d9d01ce
to
f3ec627
Compare
f3ec627
to
0baa98a
Compare
Description
This PR is for changing the Confirm button text to Create Motion when creating a motion.
New stuff ✨
Changes 🏗
Example:
(Resolves | Contributes to) #3503