Issue #580 2 ldd tool not including permissible value in dd doc book file #582
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DocBook file. Fixed bug that create problems in generated .xsd files.
Continue to make changes to fix problem with LDDTool output. Changes to use new value of "local_identifier" i.e., nameSpace:local_identifier consistently for attributes, classes, and dot.notation e.g.,pds.Internal_Reference
jshughes
deleted the
Issue_#580_2_LDDTool_not_including_permissible_value_in_DD_DocBook_file
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #580 : LDDTool not including permissible value in DD DocBook file.
Found and fixed problem with LDDTool output.
Changes to use new value of "local_identifier". Using nameSpace:local_identifier consistently for attributes, classes, and dot.notation e.g.,pds.Internal_Reference
Resolves #580