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

Make more use of getBackend to DRY things #20

Closed
taoeffect opened this issue Aug 1, 2023 · 0 comments · Fixed by #21
Closed

Make more use of getBackend to DRY things #20

taoeffect opened this issue Aug 1, 2023 · 0 comments · Fixed by #21
Assignees
@snowteamer
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@taoeffect
Copy link
Member

Problem

In a few places in the code we repeat the concept of figuring out what backend we're dealing with.

Solution

In those situations, use the new getBackend functions as described here: #16 (comment)

(Modifying things if necessary to DRY stuff)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@snowteamer snowteamer

Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use CIDs for content addressing rather than plain hashes snowteamer/chel
2 participants
@taoeffect @snowteamer