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

Contextvars powered decoupled data and client OOP API design #4

Open
WizzyGeek opened this issue May 9, 2024 · 0 comments
Open

Contextvars powered decoupled data and client OOP API design #4

WizzyGeek opened this issue May 9, 2024 · 0 comments
Labels
bikeshedding enhancement New feature or request help wanted Extra attention is needed

Comments

@WizzyGeek
Copy link
Member

Description

Designing an OOP API which decouples client and data, while providing a seamless OOP API which is performant enough to compete with the naive solution of binding data and client.

Goals

  • Comfortable
  • Implicit
  • Intuitive
  • Allows for another client to perform the action somewhat wasily
  • Performant
  • Data and client decoupling

Non-goals

  • Multi-client support, while that arises from decoupling it is not the ultimate goal.
@WizzyGeek WizzyGeek added enhancement New feature or request help wanted Extra attention is needed bikeshedding labels May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bikeshedding enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant