Skip to content

#630: Allowed hash mark as an alternative revision separator. - #638

Open
redcatbear wants to merge 9 commits into
mainfrom
feature/630_tweak_syntax_of_ids
Open

redcatbear wants to merge 9 commits into
mainfrom
feature/630_tweak_syntax_of_ids

Conversation

@redcatbear

Copy link
Copy Markdown
Collaborator

In order to avoid crossed out name part of specification item IDs that are embedded in a Markdown file but not enclosed in backticks, we allow the second tilde to alternatively be a hash mark.

@github-project-automation github-project-automation Bot moved this to 📫 Backlog in OpenFastTrace Oct 23, 2026
@redcatbear redcatbear self-assigned this Oct 23, 2026
@redcatbear redcatbear moved this from 📫 Backlog to 🔨 In Progress in OpenFastTrace Oct 23, 2026
@redcatbear

Copy link
Copy Markdown
Collaborator Author

@kaklakariada, this PR solves the Markdown problem @koppor brought up. I did some light refactoring in the course of this PR to remove some redundancy between having a specification item ID pattern and a parser that does not use it. Took a while, but I like how it turned out.

@sonarqubecloud

Copy link
Copy Markdown

Comment thread doc/changes/changes.md Resolved
/** Separator between name and revision in an item ID. */
/**
* Separator between name and revision in an item ID.
* @deprecated with 4.12.0 we widened the accepted separators to include '#'.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a link to the new constant REVISION_SEPARATOR

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am assuming you mean the pattern. Done.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: 🔨 In Progress

Development

Successfully merging this pull request may close these issues.

2 participants