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

✨(backends) more granular backends #464

Closed
wants to merge 3 commits into from
Closed

Conversation

SergioSim
Copy link
Collaborator

Purpose

We want to have a base backend class that all other backends could inherit from.
This might be useful for backend discovery in the future plugin architecture.
Also, we want to know in advance what methods of a backend are functional before backend instantiation.

Proposal

  • add BaseBackend
  • add more granular data backend interfaces or rely upon a class variable to get supported/unsupported methods (to be decided)

We want to have a base backend class that all other backends
could inherit from.
We refactor common backend settings (locale/chunk_size) to
avoid their repetition.
The current implementation of data backends leads to some repetition
among backends. We try to limit that using the template method pattern.
@SergioSim
Copy link
Collaborator Author

This PR has been split into smaller PRs: #501 #510 #511 #512 #513 #515 #517 #518

@SergioSim SergioSim closed this Nov 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants