Skip to content

Export PinsApi as RemotePinningServiceClient #2

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.

Sign up for GitHub

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

Jump to bottom
Closed
lidel opened this issue Mar 21, 2022 · 1 comment · Fixed by #4
Closed

Export PinsApi as RemotePinningServiceClient #2

lidel opened this issue Mar 21, 2022 · 1 comment · Fixed by #4
Assignees
@SgtPooki
Labels
released
Milestone
Ready for initial...

Comments

@lidel
Copy link
Member

lidel commented Mar 21, 2022 •
edited
Loading

Filling issue so we don't forget to rename PinsApi and basePath.
See my comments in #1 (review) for details.
@SgtPooki SgtPooki mentioned this issue Mar 25, 2022
Merged
@SgtPooki SgtPooki added this to the Ready for initial release milestone Mar 25, 2022
SgtPooki added a commit that referenced this issue Mar 28, 2022
@SgtPooki
fix: Export PinsApi as RemotePinningServiceClient
f023519 
fix #2
@SgtPooki SgtPooki mentioned this issue Mar 28, 2022
Merged
@github-actions
Copy link

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SgtPooki SgtPooki

Labels
released
Projects
None yet
Milestone
Ready for initial release
Development

Successfully merging a pull request may close this issue.

feat: create docs & client ready for npm release ipfs-shipyard/js-pinning-service-http-client
2 participants
@lidel @SgtPooki