-
Notifications
You must be signed in to change notification settings - Fork 23
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
Should we upstream these type classes? #512
Comments
This is one for the grand masters of this repo 😆 cc @carbolymer @Jimbo4350 @newhoggy |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
Could use an answer on this before we factor this out of our repository. |
I'd be for upstreaming. We can give it final shape on a PR level. |
Draft here #537 |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
We have been using a type-class based wrapper around cardano-api to deal with era witnesses. The classes we have are similar to
IsShelleyBasedEra
from this repository and have consistent naming with it, and can be found here:https://github.com/input-output-hk/hydra/tree/master/cardano-api-classy/src/Cardano/Api/Class
Wondering whether these are worth upstreaming here, as this library has a minimal footprint.
The text was updated successfully, but these errors were encountered: