When a post is edited to change visibility, related controls don't change

[wlonk]

Specifically, the "boost" button remains hidden/shown per the previous visibility.

Perhaps related to #24?

[toBeOfUse]

It's a fair cop. The current design is, when a user submits an edit, the server sends the newly rendered updated post content to the user who just made the edit, and then the controls around it are manually updated if necessary by frontend JavaScript, except there are a couple of things that that misses at the moment. Modifying the post controls with frontend code is messy and liable to break upon small changes to said post controls, so my proposed solution would be to factor code out of the /showposts route in viewingSweet.js to create a renderPostAndContainerHtml function, then use that function to render the whole post, controls and all, both in the /showposts route where that code is currently and in the /saveedits route in postingToSweet.js, to send to the editing client after the edit is saved.

…

On Tue, Jan 21, 2020 at 5:49 PM Kit La Touche ***@***.***> wrote: Specifically, the "boost" button remains hidden/shown per the previous visibility. Perhaps related to #24 <#24>? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#173>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL3NDOUD3CQCMW5EQHHEGQ3Q653WPANCNFSM4KJ4OU5Q> .

[wlonk]

Yeah, barring a rewrite with a pure-functional render framework (such as React/Redux, though I personally am a Vue advocate), which is Too Big to be Justified at this point, heavier use of a partials-pattern, like you describe, is the best route, I think.