Chrome: Fix post visbility when saving a post #889
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.
Posts with a "public" status and a empty string password were being considered "protected" while posts with "public" status and a null or undefined password were being considered "private". This distinction was necessary to allow us to check "password protected" visibility and display an empty password at the same time.
The problem with this is that saving a post automatically fills the password with an empty string which was being considered as password protected.
This fixes the issue by considering all nullable values for the password as "public" posts and introduce a local state in the visibility selector to display the password input even if the password is empty.