Skip to content

Conversation

Chaho12
Copy link
Member

@Chaho12 Chaho12 commented May 29, 2025

Related issue

trinodb/trino#25884

Content

Document code style guide in development/Contribute page

Test

local test
image

@Chaho12 Chaho12 requested a review from mosabua May 29, 2025 06:33
@mosabua
Copy link
Member

mosabua commented Jun 10, 2025

Please move the section down after Contribution process .. and maybe we want to expand it some more.. I have to look and compare it to the docs in the trino repo .. ideally it could be a complete move but that could happen later

@Chaho12 Chaho12 force-pushed the feature/jyoo/document-code-style branch from f703b85 to e2376dc Compare June 11, 2025 00:56
@Chaho12
Copy link
Member Author

Chaho12 commented Jun 11, 2025

Moved it. Sure, just let me know if there are further changes to make.


All contributions must follow the project's code style guidelines to ensure
consistency and readability. For Java code, follow the [Trino Java code style guide](https://github.com/trinodb/trino/blob/master/DEVELOPMENT.md#code-style).
For SQL and documentation, refer to the respective sections in the [development guide](https://github.com/trinodb/trino/blob/master/DEVELOPMENT.md).
Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

IDK what happened but fixed it. Thx for pointing it out!

@Chaho12 Chaho12 force-pushed the feature/jyoo/document-code-style branch from e2376dc to be9b17c Compare June 12, 2025 01:45

All contributions must follow the project's code style guidelines to ensure
consistency and readability. For Java code, follow the [Trino Java code style guide](https://github.com/trinodb/trino/blob/master/.github/DEVELOPMENT.md#code-style).
For SQL and documentation, refer to the respective sections in the [development guide](https://github.com/trinodb/trino/blob/master/.github/DEVELOPMENT.md).
Copy link
Member

Choose a reason for hiding this comment

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

Where is the style about SQL in this page?

Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Member

@mosabua mosabua left a comment

Choose a reason for hiding this comment

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

Formatting fixes ideally go into a separate commit but since they are minimal it might be fine. Over time I think it would be great to lift the whole section from the readme into here, but this is a great start and good enough for now.


All contributions must follow the project's code style guidelines to ensure
consistency and readability. For Java code, follow the [Trino Java code style guide](https://github.com/trinodb/trino/blob/master/.github/DEVELOPMENT.md#code-style).
For SQL and documentation, refer to the respective sections in the [development guide](https://github.com/trinodb/trino/blob/master/.github/DEVELOPMENT.md).
Copy link
Member

Choose a reason for hiding this comment

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

consistency and readability. For Java code, follow the [Trino Java code style guide](https://github.com/trinodb/trino/blob/master/.github/DEVELOPMENT.md#code-style).
For SQL and documentation, refer to the respective sections in the [development guide](https://github.com/trinodb/trino/blob/master/.github/DEVELOPMENT.md).

Before submitting a pull request, please format your code and check for style issues.
Copy link
Member

Choose a reason for hiding this comment

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

Not sure we need this here vs in the process higher up or at all ..

Copy link
Member

Choose a reason for hiding this comment

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

If we leave .. we should reword to avoid "please" and be direct .. if the code it not formatted it will actually not even pass the build .. you could just say that its a requirement for a PR therefore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants