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

Scope remaining features necessary to reach feature parity #212

Open
KendallWeihe opened this issue May 15, 2024 · 3 comments
Open

Scope remaining features necessary to reach feature parity #212

KendallWeihe opened this issue May 15, 2024 · 3 comments
Assignees

Comments

@KendallWeihe
Copy link
Contributor

KendallWeihe commented May 15, 2024

We need to scope the remaining set of features necessary to be considered at "feature parity" with the other SDKs. It's going to be a bit of an art because there is no single SDK which is identical to the other, but we should be able to come to a consensus.

One way to consider the output of this work is to define a set of unit tests, a la test driven development.

This work may include redesigning existing features within this code repo.

cc @kirahsapong @nitro-neal

@KendallWeihe
Copy link
Contributor Author

@KendallWeihe
Copy link
Contributor Author

We'll need to account for #215 prior to being considered "feature parity" -- albeit if I'm understanding things correctly this is a divergence from most of our other SDKs, where peer dependencies run rampant, I think this is a divergence worthwhile because offloading version compatibility matching to the consumer developer seems like a non-starter to me.

@KendallWeihe
Copy link
Contributor Author

This is still the active focus at this moment, but has evolved into broader design considerations

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

No branches or pull requests

1 participant