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

refactor InMemoryURIResolver #1369

Closed
jurgenvinju opened this issue Feb 27, 2020 · 1 comment
Closed

refactor InMemoryURIResolver #1369

jurgenvinju opened this issue Feb 27, 2020 · 1 comment
Assignees

Comments

@jurgenvinju
Copy link
Member

It would be better if we have one memory:// scheme which hosts for every authority string a different in-memory file-system.

The existing in memory schemes which inherit from the currently abstract InMemory resolver could be rewritten to logical schemes, e.g. test-modules:// would resolve to memory://test-modules/.

The benefit is that more in-memory file systems can be instantiated without adding more code, and also it becomes transparent which schemes are in-memory filesystems (they would all have the memory scheme.

@DavyLandman
Copy link
Member

this has been done recently.

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

No branches or pull requests

2 participants