This repository was archived by the owner on Jan 12, 2024. It is now read-only.
Fix issues with using absolute paths in docgen #680
Merged
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The previous version of the new docgen tool works correctly when using relative paths, but fails when using absolute paths on Windows. Upon investigation, this comes down to three distinct issues:
qsc.dllwas stripping one of the two quotation marks (Assembly property values set from within response files cannot end with quote marks #679)qsc.dllwas truncating assembly properties at the first colon (Assembly property values set from within response files cannot end with quote marks #679)This PR fixes all three issues, and adds more diagnostics to the documentation writer component to help understand future issues.