feat: specify transition names within documents batch #2007
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
shumkov
requested changes
Jul 25, 2024
| } | ||
| } | ||
| } | ||
| format!("DocumentsBatch({:?})", document_transition_types) |
There was a problem hiding this comment.
It may not work for all cases. DocumentsBatch can contain dozens of transitions when we remove the limitation. This is going to blow up logs where we use names. Would you like a separate method for this?
QuantumExplorer
deleted the
feat/more-precise-names-for-document-transitions
branch
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.
Issue being fixed or feature implemented
The name() function for state transitions only returned "DocumentsBatch" but it would be nice if it was more specific.
What was done?
Instead of just "DocumentsBatch" it's now "DocumentsBatch([vector_of_transition_names])". For example "DocumentsBatch(["Create", "Create", "Delete", "UpdatePrice"])".
How Has This Been Tested?
TUI
Breaking Changes
Checklist:
For repository code-owners and collaborators only