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

Completely decouple config parsing from Client construction #504

Closed
Tracked by #561
randomir opened this issue Nov 23, 2021 · 0 comments · Fixed by #568
Closed
Tracked by #561

Completely decouple config parsing from Client construction #504

randomir opened this issue Nov 23, 2021 · 0 comments · Fixed by #568
Labels
feature

Comments

@randomir
Copy link
Member

Recently refactored dwave.cloud.config.load_config() is in a good shape, but we want to completely decouple config parsing from Client construction, so that config can be loaded independently and used outside of Client -- for example in dwave.cloud.api.client.DWaveAPIClient, its subclasses and by dwave.cloud.api.resources.*.

This should be combined with #426. And then #490, #440, #357 and other config improvements can follow.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Consolidate config parsing and validation randomir/dwave-cloud-client
1 participant
@randomir