-
Notifications
You must be signed in to change notification settings - Fork 8
Reformat source code for consistent style #13
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
Conversation
b8e7c99 to
3c13302
Compare
mosabua
left a comment
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.
Looks good. Please update the commit message to something like
Reformat source code for consistent style
* Enable eslint and prettier config for validation during build
* No functional code changes, source code format only
Also maybe add info about this command to the readme file so developers know without looking at gha definition.
|
Thoughts @nineinchnick @wendigo @georgewfisher ? |
wendigo
left a comment
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've reviewed configuration for prettier + workflow + ignore files.
I'd extract the automatic changes to a separate commit.
* Enable eslint and prettier config for validation during build * No functional code changes, source code format only
|
Looks good to me. Merging. |
Description
This PR introduces standardized code formatting by adding
.prettierrcand.eslintrc.cjsfiles, using the same style rules and npm targets (such ascheck,lint) as the main Trino Preview UI codebase. This ensures consistent code style across both codebases.Additional context and related issues
All existing files have been reformatted to align with the new style rules. This PR contains only formatting changes and no new functionality or behavioral changes are introduced.