-
Notifications
You must be signed in to change notification settings - Fork 3
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
Conversation
remove before merging in to main
captured in the demo
Co-authored-by: Santi-3rd <[email protected]>
test: can edit form e2e tests
|
||
let res = suite.get(); | ||
|
||
const cn = classnames(suite.get(), { |
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'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?
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 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?
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 created this story to track the rename: #3210
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.
Had just one comment about a two-letter variable, but otherwise PR looks good.
🎉 This PR is included in version 1.16.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
What changed
Issue
#310 #3098
How to test
Screenshots
If relevant, e.g. for a front-end feature
Definition of Done Checklist