Removed unnecessary *ngVars from ThumbnailComponent #3221
Merged
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 removes the unnecessary
*ngVar
s in theThumbnailComponent
. When you disable caching and you run dspace in prod mode you will still be able to see that the content is retrieved twice, but this can't be avoided. The first time it is triggered by the SSR and the second time by CSR. We can't change that, but we should still remove the*ngVar
s since they are actually not necessary and*ngVar
s also triggerfixture.detectChanges()
every time there is interaction with the template so that's not really good for performance.Instructions for Reviewers
We actually don't need those
BehaviourSubject
s because we don't subscribe to them except in the template, so I just converted them back to regular string/boolean fields. Everything should still work like they did before.Checklist
main
branch of code (unless it is a backport or is fixing an issue specific to an older branch).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.