Synced the imports of the custom theme with the imports of the base component so custom theme works again #2984
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.
References
Description
This PR fixes the issue where running the DSpace UI with the "custom" theme resulted in many features not working properly. The root cause was identified as the themed components having mismatched imports compared to their base components. The PR addresses this by ensuring that all themed components have the same imports as their base components.
Instructions for Reviewers
The changes made in this PR include:
Testing Instructions:
yarn build:prod
and serve usingyarn serve:ssr
.Checklist
yarn lint
yarn check-circ-deps
)package.json
), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.