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.

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

Any work expected on this repo? #7

Open
justSteve opened this issue Jan 5, 2025 · 1 comment
Open

Any work expected on this repo? #7

justSteve opened this issue Jan 5, 2025 · 1 comment

Comments

@justSteve
Copy link

I've pinpointed an issue with the scope string included (the 'CRYPTO errored cuz my acct doesn't include it). And I think it'd be better to not hardcode the ts_state.json name. I can submit a PR if you are intending to resume work here.

I see you've started work on the streaming endpoints. Care to share hurdles you've faced?

thx

@jkerenyi
Copy link

jkerenyi commented Jan 8, 2025

I agree the scope string should be configurable, as a new user I got past that issue by manually editing it but the call to easy_client should allow the user to specify which permissions are to be requested. I also agree ts_state.json should not be hard-coded; I would like to be able to write it to disk in encrypted format since it's sensitive information, so returning the data and having the caller provide it each time they need to use the API would be a cleaner way to do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants