ConfusedVorlon

note this also breaks updating, because by the time we actually try to save an update, the bar has already been deleted, so the association fails to find the bar...

thanks for the super-quick response. My google-foo is clearly not up to scratch! would you accept a pull request to add a short note to this effect in the main...

not sure if my issue is related, but I'm following through from the linked minitest issue. using rspec rails I get intermittent ` Mysql2::Error: MySQL client is not connected: BEGIN`...

note: adding strict:false to my database.yml didn't fix the issue

setting slug_limit directly in the model works without an issue initialiser is as generated by friendly_id

update: the wrapper above doesn't work in an ObserveableObject in that scenario, the best I could see is ``` class Pref:ObservableObject { @SwiftyUserDefault(keyPath: \.userLastLoginDate, options: [.observed]) var userLastLoginDate: Date {...

And in the multi-document scenario where there isn't a shared prefs object ``` extension DefaultsKeys { var magnifyRotation: DefaultsKey { .init("magnifyRotation", defaultValue: false) } } class Prefs:ObservableObject { @SwiftyUserDefault(keyPath: \.magnifyRotation,...

I never came up with a good solution that integrated nicely with SwiftyUserDefaults

you can use xcode colour sets the buttons are drawn correctly according to the dark-mode when they are initially created (e.g. they don't respond to dark-mode changes)

I dunno - I like the simplicity & auto-updating of app store. I know I can manage that through brew - but I tend not to.