Fix "fileActions.currentFile" not set before using it #7624
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.
Follow-up fix for the second commit of #7591
When an empty area of a file row was clicked and the Details action was executed
fileActions.currentFile
was not guaranteed to be set to the appropriate object (it depended on the previous actions of the user), so when it was used bygetCurrentMimeType()
and other FileActions functions they may not work as expected. Now it is explicitly set to the appropriate value before its use.