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

Fix use of 'dummy' parts of SRS sections for linking purposes #1076

Open
JacquesCarette opened this issue Dec 8, 2018 · 1 comment
Open
Assignees
Labels
needs-action-items A clear 'path to resolution' is needed to close any ticket. needs-clarification Needs a clear 'state', 'goal', 'analysis', and 'explanation' to reduce solution ambiguities.

Comments

@JacquesCarette
Copy link
Owner

See PR #1075 which has one instance of this in the code. There are more. This may require some design.

@samm82
Copy link
Collaborator

samm82 commented Nov 9, 2022

Is SRS.inModel [] [] below what you mean by "dummy part of an SRS section"?

IOrgSec organizationOfDocumentsIntro inModel (SRS.inModel [] []) EmptyS],

What would the desired behaviour be?

@balacij balacij added needs-action-items A clear 'path to resolution' is needed to close any ticket. needs-clarification Needs a clear 'state', 'goal', 'analysis', and 'explanation' to reduce solution ambiguities. labels Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-action-items A clear 'path to resolution' is needed to close any ticket. needs-clarification Needs a clear 'state', 'goal', 'analysis', and 'explanation' to reduce solution ambiguities.
Projects
None yet
Development

No branches or pull requests

3 participants