-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
chore(version): update cs3d version and add iframe documentation #3474
Conversation
✅ Deploy Preview for ohif-platform-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for ohif-dev canceled.
|
Codecov Report
@@ Coverage Diff @@
## master #3474 +/- ##
=======================================
Coverage 38.27% 38.27%
=======================================
Files 82 82
Lines 1348 1348
Branches 303 303
=======================================
Hits 516 516
Misses 666 666
Partials 166 166 Continue to review full report in Codecov by Sentry.
|
You need to make sure that the viewer is also built with PUBLIC_URL set to the same path. For example, if you using | ||
`<iframe src="./ohif" />` (which means there is a `ohif` folder containing the build in your main app), then you need to: | ||
|
||
1. use a config file that is using the `routerBasename` of `/ohif` (note the one / - it is not /ohif/). |
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.
To maybe make step 2 less verbos, say. "use a config file (say myConfig.js) that has routerBasename
set to \ohif
(note the one / - it is not /ohif/)."
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.
I don't have a myConfig.js so I think it is fine to explain a bit more
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.
By adding "(say myConfig.js)" you are saying exactly that to "pretend the config file is named myConfig.js". So please reconsider adding it in.
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 good. A few changes to make. Thanks so much.
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.
Just a few more wording issues to clean up. Thanks for doing this. It will definitely come in handy.
Context
Changes & Results
Testing
Checklist
PR
semantic-release format and guidelines.
Code
etc.)
Public Documentation Updates
additions or removals.
Tested Environment