-
Notifications
You must be signed in to change notification settings - Fork 40
feat(backend/sdoc_source_code): Linux Kernel Template proposal: auto-generate SPDX-Req-ID and SPDX-Req-HKey #2555
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
Merged
Conversation
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
d900fed to
674a7c5
Compare
stanislaw
added a commit
that referenced
this pull request
Nov 14, 2025
…uments for better readability The upcoming PR #2555 adds some more variables to this class, and it feels like it is time to enforce the explicit argument names every time this class's constructor is called.
stanislaw
added a commit
that referenced
this pull request
Nov 14, 2025
…uments for better readability The upcoming PR #2555 adds some more variables to this class, and it feels like it is time to enforce the explicit argument names every time this class's constructor is called. This should help with avoiding the issues when a wrong position argument can be set in place of the right one.
stanislaw
added a commit
that referenced
this pull request
Nov 14, 2025
… arguments for better readability The upcoming PR #2555 adds some more variables to this class, and it feels like it is time to enforce the explicit argument names every time this class's constructor is called. This should help with avoiding the issues when a wrong position argument can be set in place of the right one.
stanislaw
added a commit
that referenced
this pull request
Nov 14, 2025
… arguments for better readability The upcoming PR #2555 adds some more variables to this class, and it feels like it is time to enforce the explicit argument names every time this class's constructor is called. This should help with avoiding the issues when a wrong position argument can be set in place of the right one.
stanislaw
added a commit
that referenced
this pull request
Nov 14, 2025
… arguments for better readability The upcoming PR #2555 adds some more variables to this class, and it feels like it is time to enforce the explicit argument names every time this class's constructor is called. This should help with avoiding the issues when a wrong position argument can be set in place of the right one.
stanislaw
added a commit
that referenced
this pull request
Nov 14, 2025
…eprocessing code comments In the upcoming #2555, it is important that all whitespace is preserved because the exact byte locations are used for writing modified source code comments back to the source files.
stanislaw
added a commit
that referenced
this pull request
Nov 14, 2025
…eprocessing code comments In the upcoming #2555, it is important that all whitespace is preserved because the exact byte locations are used for writing modified source code comments back to the source files.
stanislaw
added a commit
that referenced
this pull request
Nov 14, 2025
… tests, add a MarkerParser-level Linux/SPDX test This change is one more fragment from a larger #2555 extracted for an easier review. The custom assertion helpers are introduced to the test_marker_lexer which reduces the test boilerplate. The marker parser-level test_80_linux_spdx_example is introduced to verify that the comments are parsed correctly. Previously this test only existed at the marker lexer level.
5643e7f to
0e25f07
Compare
0e25f07 to
af9f595
Compare
6360bbb to
7be34cf
Compare
haxtibal
reviewed
Nov 15, 2025
haxtibal
reviewed
Nov 15, 2025
haxtibal
reviewed
Nov 15, 2025
haxtibal
reviewed
Nov 15, 2025
Contributor
|
Everything I've commented here can also be addressed in upcoming PRs. Approving right now, please decide on your own what to address now or later. |
haxtibal
reviewed
Nov 15, 2025
haxtibal
reviewed
Nov 15, 2025
haxtibal
reviewed
Nov 15, 2025
haxtibal
reviewed
Nov 15, 2025
haxtibal
reviewed
Nov 15, 2025
tests/unit/strictdoc/backend/sdoc_source_code/test_marker_parser.py
Outdated
Show resolved
Hide resolved
haxtibal
approved these changes
Nov 15, 2025
7be34cf to
ba2ed72
Compare
…generate SPDX-Req-ID and SPDX-Req-HKey
…generate SPDX-Req-ID and SPDX-Req-HKey (code review)
ba2ed72 to
d430104
Compare
haxtibal
added a commit
to haxtibal/strictdoc
that referenced
this pull request
Nov 25, 2025
…DE_STRING_VALUE strictdoc#2554 added dedent logic, strictdoc-project#2555 added hash generation. that hash results for same input were different on Windows and Linux even if CR LF was normalized to LF. Further investigation revealed that dedent logic didn't work as expected on Windows, because CR LF got split half into the string token, and half into the newline token, which in turn confused the dedent logic. By trial it turned out that "/[^\n\r]+/x" (verbose regex mode, real newlines) is not the same as "/[^\\n\\r]+/" (normal regex mode, symbolized newlines). The former wrongly lets lark scan a \r into NODE_STRING_VALUE. Thus change to the latter pattern.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.