-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(bbs): extract bbs logic into separate module #1035
feat(bbs): extract bbs logic into separate module #1035
Conversation
Signed-off-by: Timo Glastra <timo@animo.id>
Signed-off-by: Timo Glastra <timo@animo.id>
Good to see all tests passing again in 0.3.0 branch :) |
I prefer the name We might also need a discussion/issue thread where we define all the packages and their names will be. Will didcomm be the core? Which didcomm will be the core? Will there even be a core? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple of questions. Nothing really major.
"name": "@aries-framework/module-bbs", | ||
"main": "build/index", | ||
"types": "build/index", | ||
"version": "0.2.2", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will all the separate modules be in version-sync?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes for now all modules in this repo will be version synced
@@ -0,0 +1,19 @@ | |||
export function testSkipNode17And18(...parameters: Parameters<typeof test>) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this prompt an output as to why they are being skipped?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope... :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you know if this is something we can add? Maybe just a console.warn
giving a small explanation and linking to an issue?
So refreshing! I have no preference with the naming but I agree with @blu3beri that we should add a discussion regarding the modularisation (once we finish this 0.3.0 though) and that it would be appropriate to indicate the reason why we are skipping node 17 and 18 tests. I know we will not forget, as it has prevented us from sleeping for months, but just in case... |
…-support openwallet-foundation#1035: Support `PartyState` and `Wallet` changes
Just my two cents about the naming, I would rather remove |
Signed-off-by: Timo Glastra <timo@animo.id>
Resolved feedback and changed name to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
…ion#1035) Signed-off-by: Timo Glastra <timo@animo.id>
Signed-off-by: Timo Glastra timo@animo.id
Fixes #948
Extract the bbs logic into a separate
@aries-framework/module-bbs
. I had to export a lot of the vc stuff from the core bloating the core imports a bit. I think this will be solved when we extract the vc logic into it's own vc package.For now I've disabled the bbs tests to run on node 17 and 18, so we will have passing CI again, with the knowledge that BBS is broken in node 17 and 18. I also set the package to private for now so that it won't be released with the 0.3.0 release and we have more time to fix it and get it ready for release.
What do we think of the name
@aries-framework/module-bbs
? Should we call it@aries-framework/bbs-signatures
? It's private for now, so we have room to rename it until we remote the private: true from the package.jsonThere's is only really ugly hack (one of the first files in the file overview) that has to do with tsyringe injection not allowing nothing to be registered for a token. We have a signing provider that is only used for bbs, and in if you don't register the bbs module it will fail. I didn't want to spend too much time to rework it, so implemented a quick workaround for now