8.0 Major Release: Control Planes 🎉✈️

[Custard7]

Control Planes are officially released! 🎉

Control Planes are now the primary way for consumers to interact with a LearnCard. A Control Plane provides an abstraction for a higher-order wallet object to initiate complex workflows while being agnostic to the means of accomplishing the workflow.

Control Planes:

• Align plugins based on primary action categories: Identity, Signing, Verification, Storage, Caching, and Communication.
• Specify interfaces for conforming plugins to implement.
• Provide execution environments that support more complex workflows.
• Allows for utilizing multiple plugins to support a particular request.
• Streamline functionality for high-quality UX requirements, such as caching and querying capabilities.
• Incentivizes plugin convergence, rather than divergence.
• Enables plugin discovery, both internal and external.

Read the Updated Documentation Here ✨

Breaking Changes

Control Planes represent a significant overhaul of @learncard/core with some key breaking changes:

• Bespoke methods are now called with wallet.invoke (so no more wallet.verifyCredential, wallet.getTestVc, etc)
  • Example: wallet.verifyCredential → wallet.invoke.verifyCredential
  • Example: wallet.getTestVc → wallet.invoke.getTestVc
• The main CRUD stuff now lives inside of planes! These can be accessed directly on the wallet, for example:
  • wallet.publishCredential is now wallet.store.Ceramic.upload
  • wallet.addCredential is now wallet.index.IDX.add
  • wallet.getCredentialsList is now wallet.index.all.get
  • wallet.resolveCredential is now wallet.read.get
• You can now call addPlugin to add plugins to LearnCards constructed by initLearnCard
• Plugins now can (and should!) depend on Control Planes

Read the Full Migration Guide Here 👀

This is a huge step for the LearnCard SDK community—thank you so much for all of your support! 🕺🚀

Well done @TaylorBeeston for spearheading this change! 👏