Skip to content
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.

Remove filesystem operations from the backend #160

Closed
1 task done
phated opened this issue May 5, 2023 · 0 comments · Fixed by #139 or #165
Closed
1 task done

Remove filesystem operations from the backend #160

phated opened this issue May 5, 2023 · 0 comments · Fixed by #139 or #165
Assignees
Labels
enhancement New feature or request

Comments

@phated
Copy link
Contributor

phated commented May 5, 2023

Problem

Currently, this backend manages caching of its CRS, but it writes to a filepath that should be maintained by Nargo.

Proposed solution

We should change the backend trait to return a CRS as bytes and Nargo can manage caching it. This will ensure that all CRS from various backends are handled in a consistent manner.

Alternatives considered

No response

Additional context

No response

Submission Checklist

  • Once I hit submit, I will assign this issue to the Project Board with the appropriate tags.
@phated phated added the enhancement New feature or request label May 5, 2023
@phated phated self-assigned this May 5, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Noir May 5, 2023
@phated phated moved this from 📋 Backlog to 🏗 In progress in Noir May 5, 2023
@phated phated linked a pull request May 5, 2023 that will close this issue
@phated phated linked a pull request May 16, 2023 that will close this issue
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in Noir May 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
Archived in project
1 participant