Skip to content
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

Get rid of traceability/# #734

Closed
nissimsan opened this issue Apr 4, 2023 · 6 comments · Fixed by #862
Closed

Get rid of traceability/# #734

nissimsan opened this issue Apr 4, 2023 · 6 comments · Fixed by #862
Assignees

Comments

@nissimsan
Copy link
Collaborator

Continued from #531, the terms we are in control over should not have "slash-hashes".

@OR13
Copy link
Collaborator

OR13 commented Aug 29, 2023

@nissimsan
Copy link
Collaborator Author

Find-replace

@nissimsan nissimsan self-assigned this Aug 29, 2023
@OR13
Copy link
Collaborator

OR13 commented Aug 29, 2023

find replace in *.yaml and *.html... if it pops back up, tooling needs to be updated.

@nissimsan nissimsan linked a pull request Aug 30, 2023 that will close this issue
@nissimsan
Copy link
Collaborator Author

Noting that the respec anchors are still generated with /#. I still think we should fix that in the tooling.

@OR13
Copy link
Collaborator

OR13 commented Sep 1, 2023

@nissimsan is it possible to fix it in the same PR?

@nissimsan
Copy link
Collaborator Author

Theoretically it is, but it is a rather different topic. I would suggest keeping it separate. But let's keep this issue open to also update how the tooling generates terms which we define.

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 a pull request may close this issue.

2 participants