You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add useLegacyInvitations boolean type to the connectionSlice.ts. True should be the default
add setUseLegacyInvitations to the reducers in the connections slice that sets wheter to use legacy invitations on the state.
Add option "Change Connection Invitation Type" with options "Legacy (RFC 0160)" and "Out Of Band" to the KBar.tsx file.
(ideally) add a way to see if we're using legacy / oob invitation from kbar (timc1/kbar)
Whenever we create an invitation we should call /oob/create-legacy-invitation if legacy is enabled, and /oob/create-invitation otherwise. In both cases we should use the return invitaiton url and encode is as a QR (as is already happening)
The text was updated successfully, but these errors were encountered:
See #87 for general context
useLegacyInvitations
boolean type to theconnectionSlice.ts
. True should be the defaultsetUseLegacyInvitations
to the reducers in the connections slice that sets wheter to use legacy invitations on the state./oob/create-legacy-invitation
if legacy is enabled, and/oob/create-invitation
otherwise. In both cases we should use the return invitaiton url and encode is as a QR (as is already happening)The text was updated successfully, but these errors were encountered: