-
Notifications
You must be signed in to change notification settings - Fork 1
statedb: merge table creation and registration into a single API #97
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
Merged
Conversation
This file contains hidden or 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
Currently, table creation and registration with the database are two separate operations, respectively performed by [NewTable] and [RegisterTable]. However, it is not actually possible to use a table before it has been registered, and it is easy to either forget to register the table altogether, or perform that too late (e.g., when using dependency injection systems such as Hive/Cell, and registration is performed via [cell.Invoke]). This commit unifies the two APIs into one, letting [NewTable] take a database as parameter, and internally performing the registration automatically. [RegisterTable] is then unexported, as no longer required to be explicitly called by consumers. This new approach additionally prevents the possibility of registering the same table with two different databases, which would have led to a broken configuration anyhow. Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
|
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.
Currently, table creation and registration with the database are two separate operations, respectively performed by [NewTable] and [RegisterTable]. However, it is not actually possible to use a table before it has been registered, and it is easy to either forget to register the table altogether, or perform that too late (e.g., when using dependency injection systems such as Hive/Cell, and registration is performed via [cell.Invoke]).
This commit unifies the two APIs into one, letting [NewTable] take a database as parameter, and internally performing the registration automatically. [RegisterTable] is then unexported, as no longer required to be explicitly called by consumers.
This new approach additionally prevents the possibility of registering the same table with two different databases, which would have led to a broken configuration anyhow.
(Leaving as draft for now, until a new version with the other fixes is tagged)