v0.21.0
Version 0.21.0 includes the following changes:
- Changed the way handing sessions work.
- The now old method only inserted the
UserSession
object to theATProtoKit
class
. This created issues with respect to how the session will be updated. This also made theSessionProtocol
protocol
useless, since developers that want to make their own session configuration will have a more difficult time doing so. This change will solve these issues.- This is a breaking change, so you’ll need to migrate your code to reflect on this. However, this is easy to do:
authenticate()
no longer has a return statement, so there’s no need to have a variable attached to it.- The
ATProtoKit
class
will replace thesession
argument that asks for aUserSession
object with aProtocolConfiguration
object. - Everything else should work from there.
- This is a breaking change, so you’ll need to migrate your code to reflect on this. However, this is easy to do:
- The now old method only inserted the
- You can now create and delete repost records with
ATProtoBluesky
. (Thanks, @andylin2004!) - Progress for support for custom user agents. (Thanks, @airowe!)
- Not everything has been hooked up yet, but for now, a user agent has been added to clients. In a future update, you will be able to add your own custom user agents.
- Moved all session-related lexicon methods to the main
ATProtoKit
class
.ATProtocolConfiguration
now accesses those methods via proxy methods.
- Added a Special Thanks section in CONTRIBUTIONS.
- Added [email protected]
- This is a configuration file for the compiler. We want to have a separate file just for compilers that are on the Swift 6.0 toolchain or higher so we can make sure the build runs successfully on each supported version.
- Progress towards renaming variables in accordance with the Swift API Design Guidelines.
- Fixed an issue where
getSession
has a decoding error.
Once again, thank you for your support. Please give feedback, bug reports, and contributions if you have time. You can also speak to me on Bluesky (@cjrriley.com) for any questions.