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
As part of the core functionality we are bringing to nosft, we would like to integrate with deezy.io and all it's APIs.
What problem are you trying to solve?
Expose browser/node library with deezy.inscriptions integration.
Why should we solve it?
We are going to integrate deezy through this library, so that everyone can benefit from the code
How do you propose to solve it?
At the beginning by just adding a deezy service that extends api service, and create all the types and methods from the deezy.io API.
What other approaches did you consider?
A different solution will be to let everyone just integrate the API directly, but then everyone will have to create the types and the integration by themself, also they will have to take care of network configuration and others.
What could go wrong?
Since this should be compiled and available for browser and node environments, there is a risk that it doesn't work on every framework, since we might have some complex dependencies.
How will you mitigate them? By testing them in both browser and node, even though, other frameworks might be useful as well
How could this system fail, and what would be the impact if it did? At this point not much, since it is not in use
The text was updated successfully, but these errors were encountered:
Integrate with Deezy.io
As part of the core functionality we are bringing to nosft, we would like to integrate with deezy.io and all it's APIs.
What problem are you trying to solve?
Why should we solve it?
How do you propose to solve it?
What other approaches did you consider?
What could go wrong?
The text was updated successfully, but these errors were encountered: