Skip to content

Conversation

@stanislaw
Copy link
Collaborator

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 stanislaw added this to the 2025-Q4 milestone Nov 14, 2025
@stanislaw stanislaw changed the title chore(backend/sdoc_source_code): MarkerParser class: require explicitarguments for better readability chore(backend/sdoc_source_code): MarkerParser class: require explicit arguments for better readability Nov 14, 2025
@stanislaw stanislaw force-pushed the stanislaw/explicit_args branch from ccd7aa3 to 54fcc6c Compare November 14, 2025 11:42
… 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 stanislaw force-pushed the stanislaw/explicit_args branch from 54fcc6c to 922a3a2 Compare November 14, 2025 11:44
@stanislaw stanislaw merged commit 79c1129 into main Nov 14, 2025
24 checks passed
@stanislaw stanislaw deleted the stanislaw/explicit_args branch November 14, 2025 12:16
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