Implementing customizable backend #54
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This trait will eventually be used as a customization endpoint for both the cluster and server.
The current goal of this PR is to get the client API functionality working. To fully make it work as intended, we need to build more of the basws-like functionality into PliantDb. That will be done over several PRs.
The last thing this PR needs is an example with docs. But I am hesitating because I'm tempted to wait to build the example until actual users are implemented. The example's complexity will not increase significantly, but then the example can show the full power of the API with comments helping people get it set up themselves. So, I may end up just merging anyways, but going to sleep on it.