-
Notifications
You must be signed in to change notification settings - Fork 13.6k
[clang-doc] switched from using relative to absolute paths #93281
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
Merged
Merged
Changes from 11 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
f3eec97
clang-doc switched from using relative to absolute paths
PeterChou1 4d4197f
remove duplicate function
PeterChou1 61e9da0
[clang-doc] modify paths for anchors in js file
PeterChou1 fd3ff81
[clang-doc] add test for asset paths
PeterChou1 f786396
[clang-doc] fix tests
PeterChou1 40a52e5
[clang-doc] fix missing - in output
PeterChou1 6b47fee
[clang-doc] fix platform
PeterChou1 ca1fb33
[clang-doc] paths
PeterChou1 3142445
[clang-doc] pr comments
PeterChou1 02a1c5a
[clang-doc] address pr comments
PeterChou1 1732676
[clang-doc] rework tests
PeterChou1 c2d9e15
[clang-doc] fix broken tests
PeterChou1 9f02856
[clang-doc] fix clang-doc error
PeterChou1 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
// RUN: rm -rf %t && mkdir %t | ||
// RUN: cp "%s" "%t/test.cpp" | ||
// RUN: clang-doc --format=html --executor=standalone -p %s --output=%t | ||
// RUN: FileCheck %s -input-file=%t/index_json.js -check-prefix=JSON-INDEX | ||
// RUN: rm -rf %t | ||
|
||
// JSON-INDEX: var RootPath = "{{.*}}"; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is there a way to make this check more meaningful? Can we match nothing in the path itself? |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like I missed this. Please don’t copy the test file around. To be blunt this pattern has been brought up in multiple PRs and even in previous incarnations of this one. Use the same conventions we’ve insisted on in other tests here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, the reason why I kept using this pattern is because I copied the same test setups in the original test for clang-doc here and here