Skip to content
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

[Deprecated] - Feat(28): Proposals creation - fields connection and cache #55

Closed
wants to merge 22 commits into from

Conversation

tplocic20
Copy link
Contributor

@tplocic20 tplocic20 commented Feb 12, 2024

Status

Cherry picking features for Tailwind refactor context

Description

  • Connected fields to contract
  • Added json validation
  • improved form state and navigation

Other changes

  • Small change in validation and flows.

Tested

Go to proposal creation and fill data. The proposal should be created with filled info

Related issues

Copy link

vercel bot commented Feb 12, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
governance-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 21, 2024 11:29am

@denviljclarke
Copy link
Contributor

Hey @tplocic20 nice work, I just pulled this up locally I noticed a few small things -

  • When a proposal is loaded from cache, I think it would be a great UX if users are automatically taken to the Proposal Description step.
  • Similar to the Proposal Description step, it would be a good UX if the next button is disabled by default and disabled whenever there's an error.
  • I know it’s not a part of this story but I’ve noticed that this section is missing

@tplocic20
Copy link
Contributor Author

tplocic20 commented Feb 13, 2024

@denviljclarke

  • When a proposal is loaded from cache, I think it would be a great UX if users are automatically taken to the Proposal Description step.

We need to start at the wallet step anyway, because there may be a chance that user is disconnected. But I will add auto "next" if the form is valid

  • Similar to the Proposal Description step, it would be a good UX if the next button is disabled by default and disabled whenever there's an error.

Did you mean enabled by default and disabled on error?

  • I know it’s not a part of this story but I’ve noticed that this section is missing

My bad - will add it

@denviljclarke
Copy link
Contributor

Did you mean enabled by default and disabled on error?

Disabled by default (because by default it's invalid right right? because it's empty), like this

Screenshot 2024-02-13 at 9 27 33 AM

But when it's empty now the next button is still enabled.

Screenshot 2024-02-13 at 9 30 23 AM

What do you think?

@denviljclarke
Copy link
Contributor

@denviljclarke

  • When a proposal is loaded from cache, I think it would be a great UX if users are automatically taken to the Proposal Description step.

We need to start at the wallet step anyway, because there may be a chance that user is disconnected. But I will add auto "next" if the form is valid

Right, I understand. It did feel a bit weird not being able to continue where I left off as soon as I chose to. It might be better not to prompt users to continue until they've reached the Proposal Description step then?

@tplocic20
Copy link
Contributor Author

Did you mean enabled by default and disabled on error?

Disabled by default (because by default it's invalid right right? because it's empty), like this

Screenshot 2024-02-13 at 9 27 33 AM

But when it's empty now the next button is still enabled.

Screenshot 2024-02-13 at 9 30 23 AM

What do you think?

The execution step is an optional value.
Contract is requiring some data there, but we do not expect user to fill it

@tplocic20
Copy link
Contributor Author

@denviljclarke

Okay, so I've fixed issues you have mentioned.
Now, when user is coming back, and he is already connected (with enough veMENTO) - will be prompted about cache and redirected to the next step automatically.

The execution step is optional, so the next button is always available.

Copy link
Member

@bayological bayological left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to run through this, for me this does not work locally.

  1. When running locally, I get this error when I have clicked the create proposal page
    image

  2. When using the preview application the page loads fine however when using execution Json that does not match the specified format, if add a new line the error goes away but I cannot proceed
    Screencast from 03-12-2024 01:17:09 PM.webm

@RyRy79261
Copy link
Contributor

I'm not able to access the /create-proposal page on vercel preview. Tried with Frame, Frame as Metamask & Metamask

image

@tplocic20 tplocic20 requested review from bayological and bowd March 14, 2024 10:45
Copy link
Member

@bayological bayological left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When running locally the form defaults to the execution json section, leaving the title and description sections blank. Please check this out, it does not happen on the preview.

@bayological
Copy link
Member

Some additional things I noticed:

The breadcrumb and title do not match what is on the figma design.

Current:
image

Figma:
image

The text displayed when a user doesn't have any locks should say:
"To create a new governance proposal, you need to lock 2,500 MENTO..."

Instead of:
"To create new governance proposal you need to lock 2,500 veMENTO."

@tplocic20
Copy link
Contributor Author

Some additional things I noticed:

The breadcrumb and title do not match what is on the figma design.

Current: image

Figma: image

The text displayed when a user doesn't have any locks should say: "To create a new governance proposal, you need to lock 2,500 MENTO..."

Instead of: "To create new governance proposal you need to lock 2,500 veMENTO."

The breadcrumbs designs changed while working on this ticket and there is a separate task to update them.
I'll update the test shortly

@tplocic20 tplocic20 requested a review from bayological March 21, 2024 11:25
@RyRy79261 RyRy79261 changed the title Feat(28): Proposals creation - fields connection and cache [Deprecated] - Feat(28): Proposals creation - fields connection and cache Apr 9, 2024
@RyRy79261 RyRy79261 closed this Apr 15, 2024
@RyRy79261 RyRy79261 deleted the feat/28-proposals-creation branch April 15, 2024 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants