* Update Sparkle to latest version
* Bump minimum macOS target
For launch, I propose we support the current version of macOS (14.x) and one version earlier (13.x).
* Add WFNavigation wrapper to use NavigationSplitView in macOS
* Replace NavigationView with WFNavigation in ContentView
* Fix deprecation warnings on locale
* Update docs for updating the Mac app
* Fix for being sent back to post list on app reactivate
* Bump build version
* Remove debugging statements
* Bump Sparkle version to address security fix
* Unset isScrollEnabled property on UITextViews
* Begin implementing common MultilineTextView
* Remove legacy text views
* Fix firstResponder issues
* Bump version and build number and update change log
* Fix smart-dashes replacement in MultilineTextView
* Wait 10ms before navigating to the editor after creating a new post
* Wait before navigating to editor after creating a new post
* Bump build number
* Embed text editor fields into ScrollView
* Bump version/build number and update change log
* Fix truncated post badges on status change
When going from a shorter label (e.g., ‘LOCAL’) to a longer one (e.g., ‘PUBLISHED’), the SwiftUI render loop would not expand the size of the post badge to fit the extra characters, so on change it would be truncated (e.g., read ‘PUBL…’). This change fixes the bug.
* Don’t render spacer in iOS 16+
* Bump version and build for TestFlight
* Bump version and build of action extension
* Run SwiftLint on all files for each build
This prevents a build warning in Xcode 14 because SwiftLint doesn’t yet support input/output files for these script execution build phases. It’s fast enough, so running it on all files isn’t an issue.
* Add missing error handling on login view
* Clean up line_length warning
* Update change log
* Initial work on presenting alert on error
* Move Account-related error handling up the hierarchy
* Handle errors on logout
* Fix for temporary debugging
* Clean up WriteFreelyModel’s published vars
* Add error handling to top-level content view
* Set current error on API call failures
* Set current error on API call handlers
* Move User Defaults errors to ErrorConstants file
* Add default values for some error strings
* Handle purging post errors
* Add FIXME to track silent failure on fetching collections
As collections are fetched and added to the `list` property in the CollectionListModel’s initializer, it’s tricky to throw an error here: we call it as a property initializer in CollectionListView, which cannot throw.
Consider refactoring this logic such that we’re using, for example, a @FetchRequest in CollectionListView instead.
* Handle errors in (most) shared code
Two outliers to come back to are:
- the LocalStoreManager, where we can’t set a current error in the WriteFreelyModel in methods that can’t throw
- the CollectionListModel, where the initializer can’t throw because we use it as a property initializer in CollectionListView
* Add error handling to Mac app
* Revert "Add error handling to Mac app"
This reverts commit b1a8b8b29c.
Fixes a bug where tapping the new-post button creates the new local draft, but doesn’t automatically load it in the post editor until you open, and then dismiss, the settings sheet.
