Ability to Set Post Language and Edit Existing Posts

[hjiangsu]

Pull Request Description

This is a PR which adds the ability to edit existing posts, and set the specified language for the post. It also adds a few UI changes to make the experience a bit more cohesive. The CreatePostPage was fully refactored to be able to take advantage of some of the comments mentioned in #853 (comment). This includes:

• Removing most (if not all) other dependencies on blocs. This was done by creating a new cubit to handle the state management for this page.
• Slight UI adjustments (mainly to community and user selectors) to match each other better
• Reworked the draft logic to be handled within the CreatePostPage. This means we no longer need the previous draft logic outside of the CreatePostPage. This does not apply to the comment page as that still retains the original logic.
  • There is a slight minor issue where the snackbar does not show up when the post draft is saved. This could be due to the CreatePostPage being removed off the navigation stack (and thus having no context)

Notes:

• With the addition of language selection, a new autocomplete has been added in to select and change the language.
• When a post is editable, the reply action on the Post page will be transformed into an edit action.

Issue Being Fixed

Issue Number: #157, #892

Screenshots / Recordings

Screen.Recording.2023-11-14.at.7.34.20.PM.mov

Checklist

• Did you update CHANGELOG.md?
• Did you use localized strings where applicable?
• Did you add semanticLabels where applicable for accessibility?

[hjiangsu]

@micahmo Feel free to review the PR if you'd like or do some testing! I think most cases were caught, but since this is a fairly big refactor, some things may have been missed (which should hopefully be caught when this is released to the nightly builds)

[micahmo]

Very nice, I especially like the draft refactoring!

[micahmo]

I was wondering if we might want to think about consolidating all the different ways we can prepopulate a post. Right now I think we have drafts, edits, and shares, each with different things that are saved/restored. (For example, is language selection saved with drafts?) Maybe we can have a wrapper class around a Post/View/Media/whatever, so that it can contain every possible field, and then an enum saying what kind of thing it is. Just a thought.

[hjiangsu]

Thats a good idea! I think we could do this in a different PR since this one already contains a pretty substantial change if thats all good with you.

[micahmo]

Of course!