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

feat: add CAN detail form #3186

Merged
merged 17 commits into from
Dec 11, 2024
Merged

feat: add CAN detail form #3186

merged 17 commits into from
Dec 11, 2024

Conversation

fpigeonjr
Copy link
Contributor

@fpigeonjr fpigeonjr commented Dec 5, 2024

What changed

  • adds can details form
  • adds validation

Issue

#310 #3098

How to test

  1. e2e test pass
  2. or login as budget team
  3. goto can detail page
  4. select current fiscal year from dropdown
  5. see edit button and click on it
  6. see form for editing can
  7. edit nickname and description(optional)
  8. save
  9. 💰 profit

Screenshots

If relevant, e.g. for a front-end feature

Definition of Done Checklist

  • OESA: Code refactored for clarity
  • OESA: Dependency rules followed
  • Automated unit tests updated and passed
  • Automated integration tests updated and passed
  • Automated quality tests updated and passed
  • Automated load tests updated and passed
  • Automated a11y tests updated and passed
  • Automated security tests updated and passed
  • 90%+ Code coverage achieved
  • Form validations updated

@fpigeonjr fpigeonjr added the javascript Pull requests that update Javascript code label Dec 5, 2024
@fpigeonjr fpigeonjr changed the title feat: add cans detail form feat: add CAN detail form Dec 5, 2024
@fpigeonjr fpigeonjr marked this pull request as ready for review December 11, 2024 20:39

let res = suite.get();

const cn = classnames(suite.get(), {
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm assuming cn stands for className or classNames? If it's not too much effort, could we potentially try to not have super short variable names in favor of readability?

Copy link
Contributor

Choose a reason for hiding this comment

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

Great idea! This naming convention is used in other FE components for form validation. Would it be okay to track it in a new tech debt ticket?

Copy link
Contributor

Choose a reason for hiding this comment

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

I created this story to track the rename: #3210

Copy link
Contributor

@rajohnson90 rajohnson90 left a comment

Choose a reason for hiding this comment

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

Had just one comment about a two-letter variable, but otherwise PR looks good.

@fpigeonjr fpigeonjr merged commit b868ee2 into main Dec 11, 2024
42 checks passed
@fpigeonjr fpigeonjr deleted the OPS-310/3098_can_details_form branch December 11, 2024 21:21
Copy link

🎉 This PR is included in version 1.16.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
javascript Pull requests that update Javascript code released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants