-
Notifications
You must be signed in to change notification settings - Fork 5
Implement line length and breaking rules #109
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
Open
jvsqzj
wants to merge
8
commits into
intel:main
Choose a base branch
from
kevv87:feature/73-line-breaking
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
6cc0d84
Add IN6 rule: continuation line support
me-cr 3f8f131
Add rule LL6 for funcall broken after left paren
jvsqzj 568cc5d
Add MethodOutputBreak (LL5) Rule (#24)
alecalvop e0b60f9
Break on conditional expression (#23)
dtarassenko 6b44a59
Implement rule LL2 for breaking before binary ops
jvsqzj d9825d1
Apply consistent naming convention for linelength rules
jvsqzj 3a3d605
Add CHANGELOG entry
alecalvop 4c336d5
Add file for srcbreak_before_binary_op tests
jvsqzj File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -47,5 +47,24 @@ Below are listed the currently supported rules for linting: | |
|
|
||
| ## Line Length | ||
| - **LL1**, `long_lines`: Lines should be kept shorter than 80 characters. This limit can be set to a custom value | ||
| - **LL2**, `break_before_binary_op`: Break long lines before binary operators, not after | ||
| ``` | ||
| x = (a_very_long_expression | ||
| + another_very_long_expression) | ||
| * a_third_long_expression; | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. indentation error in example? |
||
| ``` | ||
| - **LL3**, `break_conditional_expression`: Break conditional expressions before the ?, or both before the ? and before the :. | ||
| - **LL5**, `break_method_output`: Break long method declarations with output parameters before the arrow. | ||
| ``` | ||
| method inquiry_status(uint64 physical_address) | ||
| -> (uint16 status) { | ||
| ... | ||
| } | ||
| ``` | ||
| - **LL6**, `break_func_call_open_paren`: Function and method invocations can be broken after the opening parenthesis, with the continuation lines indented one level. | ||
| ``` | ||
| signal_interface *my_interface = SIM_get_interface( | ||
| other_object, SIGNAL_INTERFACE); | ||
| ``` | ||
|
|
||
| ##### Check [Issue #76 For remaining and planned checks](https://github.com/intel/dml-language-server/issues/76) | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Should probably primarily focus on user-friendly version of description of what linting has improved (this is allowed to be vague, or just a reference to the rule number in-doc), followed by the identifier of the linting rules (this is still valuable feedback, as these now also appear in linting messages)