-
Notifications
You must be signed in to change notification settings - Fork 16
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
update custom issue template backend tickets #1015
base: main
Are you sure you want to change the base?
update custom issue template backend tickets #1015
Conversation
❌ Deploy Preview for starter-dev failed.
|
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.
the comment here is linked to what we agree on the FE ticket
@@ -2,6 +2,11 @@ | |||
|
|||
Having code style consistency is important for any project. A standardized set of options should be set that can be overwritten by the implementer at a later date. | |||
|
|||
- ESLint: Code formatting should be enforced via ESLint rules. Rules should be set to the strictest setting and enforced via CI. The standard rules for a stack should be selected and if there are specialized plugins, those should be utilized and appropriately tuned. |
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.
same comment as the FE ticket changes. i think this is too strict.
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.
Kudos, SonarCloud Quality Gate passed! |
Type of change
Summary of change
Checklist