Skip to content
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

[Dev]: Switch to SquireSDK #66

Open
TylerBloom opened this issue Mar 2, 2023 · 1 comment
Open

[Dev]: Switch to SquireSDK #66

TylerBloom opened this issue Mar 2, 2023 · 1 comment
Assignees
@TheDeveloper101
Labels
good first issue Good for newcomers todo Will be resolved but work hasn't started
Milestone
SquireCore Integr...

Comments

@TylerBloom
Copy link
Member

Unmet Need:

Currently, SquireBot uses the SquireLib library directly. However, it will need access to the squire client and other things that the SDK provides. Since the SDK re-exports SquireLib, all references to SquireLib need to be changed to the SDK.
@TylerBloom TylerBloom added good first issue Good for newcomers todo Will be resolved but work hasn't started labels Mar 2, 2023
@TylerBloom TylerBloom added this to the SquireCore Integration milestone Mar 2, 2023
@TylerBloom
Copy link
Member Author

This is blocked by #65

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

@TheDeveloper101 TheDeveloper101

Labels
good first issue Good for newcomers todo Will be resolved but work hasn't started
Projects
Squire Tournament Services
Status: No status
Milestone
SquireCore Integration
Development

No branches or pull requests
2 participants
@TylerBloom @TheDeveloper101