Skip to content

Conversation

@Mooan
Copy link
Contributor

@Mooan Mooan commented Sep 14, 2025

Hi,

This is my first contribution to the project. Thank you for maintaining this excellent tool!

As discussed in Question about line marker specification: @relation(scope=line) targeting behavior thread, I've implemented Option B LineMarker.

Changes:

  • Treat LineMarker as a 1-line range
  • Validate semantics: disallow consecutive LineMarkers and LineMarker at EOF; raise StrictDocSemanticError.
  • HTML source: add is_range_marker(); fix range-closer for line/range markers
  • Update unit/integration tests

Please let me know if you need any changes or have any feedback. I'm happy to make adjustments as needed.

Thank you for your time reviewing this!

- Treat LineMarker as a 1-line range
- Validate semantics: disallow consecutive LineMarkers and LineMarker at EOF; raise StrictDocSemanticError.
- HTML source: add is_range_marker(); fix range-closer for line/range markers
- Update unit/integration tests
@stanislaw stanislaw merged commit 9207ef0 into strictdoc-project:main Sep 16, 2025
33 checks passed
stanislaw added a commit that referenced this pull request Sep 16, 2025
This change makes both language-aware and unaware parsers to use the same line marker validation function.

This is a follow-up to: #2458
stanislaw added a commit that referenced this pull request Sep 16, 2025
This change makes both language-aware and unaware parsers to use the same line marker validation function.

This is a follow-up to: #2458
@stanislaw
Copy link
Collaborator

Hey @Mooan, thanks a lot for contributing this!

I have opened a follow-up MR that extends your code to also work for Python/C/Robot parsers: #2460.

While testing your branch, I also found an unrelated JS bug #2461 which I would like to fix before releasing a new Pip version.

If you want to start using the new patch already, feel free to install the Nightly version as described here: https://strictdoc.readthedocs.io/en/latest/latest/docs/strictdoc_01_user_guide.html#3.3-Installing-nightly-StrictDoc-as-a-Pip-package.

stanislaw added a commit that referenced this pull request Sep 17, 2025
…r decision

This fixes a bug introduced in #2458 that we missed to catch during the code review. Luckily this work has not been released yet.

In the future, we need to write an e2e test that catches this error.

Fixes #2461
@stanislaw stanislaw modified the milestones: 2025-Q4, 2025-Q3 Oct 5, 2025
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.

2 participants