-
Notifications
You must be signed in to change notification settings - Fork 803
Content viewer composable #13533
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
Content viewer composable #13533
Conversation
Build Artifacts
|
20ba899
to
9b4be6f
Compare
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.
Code review looks good to me -- the approach is straightforward and the renaming within the diff lines up. I will do a confirmation on Monday that we aren't missing any of the replacements for the renaming (I haven't grepped everything yet). But, I think this is ready for manual QA. @pcenov and @radinamatic, can this go on the to-do list?
return component; | ||
} | ||
|
||
logger.warn( |
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.
👍
9b4be6f
to
69430d0
Compare
Found two issues after reviewing all types of resources from the QA channel:
Tested in Chrome and Firefox on Ubuntu. |
I am very confident the PhET 404s are pre-existing. Will fix the other two issues. |
48bda60
to
8c08662
Compare
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.
All resource types now check out! 💯 🎉
Deprecate ContentRenderer mixin and ContentRenderer API. Migrate usage of ContentRenderer to ContentViewer. Rename code and docs to prefer 'viewer' to 'renderer'.
Consolidate content viewer props. Remove stale prop passing for unused/nonexistent props.
8c08662
to
3b08b57
Compare
Re-testing after the latest commits was uneventful, all resources are opening and displaying correctly! Merge away! 🚀 💥 |
Summary
props
andcontext
arguments to the setup function as arguments, and an options object for additional configuration - currently this is only used for the defaultDuration for duration based progress calculations, which was previously provided by a public computed prop.References
Fixes #12744 (mostly) the deprecation warnings and handling can be cleaned up in develop.
Reviewer guidance
Does every content viewer still work (use the QA Channel to test this)?
Have I got every important instance of
renderer
as nomenclature? (noting I deliberately did not update the CustomChannelRenderer at this point, because it is a) possibly broken, and b) not easily tested).Have I updated every instance of an error being emitted by a component and instead used the
reportError
method?A lot of this work was done by Claude code, but the 'renderer' renaming I did just using VSCode find replace tooling to be more surgical.
I have manually tested every content viewer.