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

WIP feat(APP-3895): Implement various UX improvements #425

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

thekidnamedkd
Copy link
Contributor

@thekidnamedkd thekidnamedkd commented Mar 12, 2025

Description

  • In the setMetadata native action, “proposed” should be listed before “existing”
  • Apply title casing to “launch” dates in details sections. (enabled by new prop on Link to specify text classnames, app will need to update)
  • Remove title casing from “By”.
  • Proposal body text is larger font than proposal summary. Should be the other way around.
  • When entering raw calldata for custom actions don’t pre-populate data with a value of “0x”. It should be placeholder text of “0x…”.
  • In the action accordion header, if address is blackhole 0x000…0000 address, don’t show the address or link to block explorer
  • All address truncation should be 0x1234…6789. Right now the 0x is counting as 2 digits and makes it look like 0x12….6789.

Task: APP-3895

Type of change

  • New feature (non-breaking change which adds functionality)

Checklist:

  • Manually smoke tested the functionality locally
  • Confirmed there are no new warnings or errors in the browser console
  • Made the corresponding changes to the documentation
  • Added tests that prove my fix is effective or that my feature works
  • Updated the CHANGELOG.md file after the [UPCOMING] title and before the latest version
  • (For User Stories only) Double-checked that all Acceptance Criteria are satisified
  • Confirmed there are no new warnings on automated tests
  • Selected the correct base branch
  • Commented the code in hard-to-understand areas
  • Followed the code style guidelines of this project
  • Reviewed that the files changed in GitHub’s UI reflect my intended changes
  • Confirmed the pipeline checks are not failing

@thekidnamedkd thekidnamedkd changed the title WIP feat(APP-3895): Implement UX improvements WIP feat(APP-3895): Implement various UX improvements Mar 12, 2025

const inputLabels = !hideLabels ? { label: name, helpText: notice } : undefined;
const formFieldName = proposalActionsDecoderUtils.getFieldName(fieldName, formPrefix);

const commonProps = { placeholder: type, className, ...inputLabels };
const commonProps = { placeholder: '0x...', className, ...inputLabels };
Copy link
Member

Choose a reason for hiding this comment

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

Couldn't find any mention to the fields placeholder on the Jira ticket, this component moreover is used for any transaction input and not just address types, so a 0x... placeholder would be wrong

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I interpreted that from below on ticket, but do agree that it's a bit tricky to extricate as the form/input relationship is fairly complex and we discussed at offsite that this has implications:
"When entering raw calldata for custom actions don’t pre-populate data with a value of “0x”. It should be placeholder text of “0x…”."

@@ -290,9 +290,6 @@ module.exports = {
},
p: {
fontSize: theme('fontSize.base'),
'@screen md': {
fontSize: theme('fontSize.lg'),
Copy link
Member

Choose a reason for hiding this comment

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

Let's double check this with design

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.

2 participants