Fix Component View Details not initialize license #253
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The previous routine intialized the selectedLicense at a time, where the component was not always present. Signed-off-by: Torsten Mehnert <torsten.mhn@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This will fix an error, that caused the License in the Legal tab of the Component details view was not set, even if the component had an resolved license.
The previous routine intialized the selectedLicense at a time, where the component was not always present. In my case the component was only present, after a hot reload during development. So initialized this field when the modal opens. I've tracked this by putting a console.log statement at the end of the
retrieveLicensesmethod. In most casesthis.componentwas an empty object.Fixes #223