-
Notifications
You must be signed in to change notification settings - Fork 535
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
Update createComponent in externalComponentLoader.ts to use the current component's path instead of WaterParkLoaderName #1208
Labels
area: framework
Framework is a tag for issues involving the developer framework. Eg Aqueduct
Milestone
Comments
curtisman
added
isomorphic
Client/server isomorphic usage issues
area: framework
Framework is a tag for issues involving the developer framework. Eg Aqueduct
and removed
isomorphic
Client/server isomorphic usage issues
labels
Feb 10, 2020
This was referenced Nov 4, 2022
This was referenced Nov 4, 2022
This was referenced Nov 5, 2022
This was referenced Nov 5, 2022
This was referenced Nov 5, 2022
jason-ha
pushed a commit
that referenced
this issue
Jan 23, 2025
…1208) Bumps [webpack](https://github.com/webpack/webpack) from 5.95.0 to 5.96.1. - [Release notes](https://github.com/webpack/webpack/releases) - [Commits](webpack/webpack@v5.95.0...v5.96.1) --- updated-dependencies: - dependency-name: webpack dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#1188 removed createSubComponent from IComponentContext. So, to create a component with a specific package path, createComponent or _createComponentWithProps in IHostRuntime is to be used.
ExternalComponentLoader was using createSubComponent to create a component relative to the current component's path. It was changed to use createComponent by prepending WaterParkLoaderName (as the root component name). This works for now but it needs to be changed to get the path of the current component.
Once #1123 is checked in, we can use it to get the current component's path and use that instead of WaterParkLoaderName.
The text was updated successfully, but these errors were encountered: