Don't set ffmpeg path from null to its Display value #6544
Merged
Conversation
This file contains 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
crobibero
approved these changes
Sep 11, 2021
Bond-009
reviewed
Sep 11, 2021
|
@jellyfin-bot rebase |
jellyfin-bot
force-pushed
the
fix_ffmpeg_path_updating
branch
from
daefa3a
to
95f3447
Compare
cvium
commented
Sep 21, 2021
cvium
changed the title
Bond-009
approved these changes
Oct 23, 2021
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
If existing path is null it means that it hasn't been set by the user, so don't set it to its Display value.
Issues
Fixes #4449