Skip to content

Conversation

@stanislaw
Copy link
Collaborator

No description provided.

@stanislaw stanislaw added this to the 2025-Q4 milestone Nov 13, 2025
@stanislaw stanislaw force-pushed the stanislaw/write_back_ast branch 4 times, most recently from d900fed to 674a7c5 Compare November 13, 2025 23:39
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.
@stanislaw stanislaw force-pushed the stanislaw/write_back_ast branch 2 times, most recently from 5643e7f to 0e25f07 Compare November 14, 2025 15:09
@stanislaw stanislaw changed the title feat(backend/sdoc_source_code): Linux Kernel Template proposal: automatic generation of SPDX-Req-ID and SPDX-Req-HKey feat(backend/sdoc_source_code): Linux Kernel Template proposal: auto-generate SPDX-Req-ID and SPDX-Req-HKey Nov 14, 2025
@stanislaw stanislaw force-pushed the stanislaw/write_back_ast branch from 0e25f07 to af9f595 Compare November 14, 2025 17:09
@stanislaw stanislaw requested a review from haxtibal November 14, 2025 17:22
@stanislaw stanislaw force-pushed the stanislaw/write_back_ast branch 4 times, most recently from 6360bbb to 7be34cf Compare November 14, 2025 23:09
@haxtibal
Copy link
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.

@stanislaw stanislaw force-pushed the stanislaw/write_back_ast branch from 7be34cf to ba2ed72 Compare November 15, 2025 10:34
@stanislaw stanislaw force-pushed the stanislaw/write_back_ast branch from ba2ed72 to d430104 Compare November 15, 2025 10:48
@stanislaw stanislaw merged commit 2ed8f9c into main Nov 15, 2025
24 checks passed
@stanislaw stanislaw deleted the stanislaw/write_back_ast branch November 15, 2025 11:15
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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants