v0.29.0
Version 0.29.0 includes the following changes:
- Added support for the following in
ATProtoBluesky:- Adding Status records.
- Removed the SwiftCBOR dependency.
- All lexicon model containers are `enums.
enums are typically used for namespaces, so this change should make more sense to use.
- Made the following changes to union
enums:- Successfully moved all of the union
enums to their appropriatestructs. - A new protocol has been created, named
ATUnionProtocol, which is now required for all of the unionenums. - Tweaked how the unions handle unknown lexicons.
- Now, if it can’t find the appropriate model, it will simply decode the model into a
[String: CodableValue]. - The only exceptions to this rule are a few
enums related totools.ozone.*lexicon models. They will not receive the same treatment until the lexicon generator is running.
- Now, if it can’t find the appropriate model, it will simply decode the model into a
ATUnionBuilderis now deprecated and will be removed in 0.31.0.- All other macros have be deprecated and will be removed once the lexicon generator has been created.
- Successfully moved all of the union
- Tweaked how union
enums handle unknown lexicons.- Now, if it can’t find the appropriate model, it will simply decode the model into a
[String: CodableValue].
- Now, if it can’t find the appropriate model, it will simply decode the model into a
- Fixed an issue where
ConsoleDebuggerwas inaccessible. - Updated the lexicon models and methods from the latest lexicon changes in bluesky-social’s atproto library.
- This doesn’t include a couple of lexicon models and methods from the
app.bsky.unspecced.*lexicons, due to the advisory not to use them.
- This doesn’t include a couple of lexicon models and methods from the
Once again, thank you for your support. Please give feedback, bug reports, and contributions if you have time. Consider starring this project if you find it helpful, and feel free to donate an amount that reflects the value it has brought to you. Your support helps ensure the continued development and improvement of this project. You can also speak to me on Bluesky (@cjrriley.com) for any questions.