You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: Fix eslint/prettier errors, add checks to CI (#26520)
## Description
<!---Describe your changes in detail-->
This is a follow on to adding eslint + prettier packages and configs
here: #26281
This is a big QOL and code quality improvement for UI development.
Formatting and linting will be consistent and enforced across the UI
codebase.
## Motivation and Context
<!---Why is this change required? What problem does it solve?-->
<!---If it fixes an open issue, please link to the issue here.-->
This keeps formatting and lint rules consistent across the whole UI
codebase, adds steps to the CI to lint + check formatting
## Impact
<!---Describe any public API or user-facing feature change or any
performance impact-->
This should have no user facing impacts
## Test Plan
<!---Please fill in how you tested your change-->
1. CI Passes
2. ESLint errors + bugs requiring manual intervention I will call out
inline in the PR. These should be tested manually.
## Contributor checklist
- [ ] Please make sure your submission complies with our [contributing
guide](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md),
in particular [code
style](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#code-style)
and [commit
standards](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#commit-standards).
- [ ] PR description addresses the issue accurately and concisely. If
the change is non-trivial, a GitHub Issue is referenced.
- [ ] Documented new properties (with its default value), SQL syntax,
functions, or other functionality.
- [ ] If release notes are required, they follow the [release notes
guidelines](https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines).
- [ ] Adequate tests were added if applicable.
- [ ] CI passed.
- [ ] If adding new dependencies, verified they have an [OpenSSF
Scorecard](https://securityscorecards.dev/#the-checks) score of 5.0 or
higher (or obtained explicit TSC approval for lower scores).
## Release Notes
```
== NO RELEASE NOTE ==
```
0 commit comments