-
Notifications
You must be signed in to change notification settings - Fork 11
chore: remove old entity traits impls [wpb-22196] #1748
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
Draft
coriolinus
wants to merge
18
commits into
main
Choose a base branch
from
prgn/chore/22196-remove-old-entity-traits-impls
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
78d9221 to
f22fe4d
Compare
Makes `V6Credential` public to allow its use in a pub trait As it appears as an associated type in a trait, it must be public.
New entity traits use `Option` instead of an error variant to indicate absence, or a `bool` in the case of a delete. We don't need these pointless error variants; the caller knows what kind of thing they had been looking for.
…functions We're at the point of 2nd-order effects now.
Also all variations of that pattern.
These examples were used during the initial design of the new entity traits and during development of the new entity implementaiton macro. However, at this point those designs are effectively locked, and these examples are not actually used for anything; pure dead code. So we get rid of them.
This macro has two major downsides: - by moving into a macro context from a `cfg`-context, it degrades IDE experience - it encourages grouping large blocks by configuration, not by item So IMO it is bad practice, and I'm excited to remove it
f22fe4d to
6bdad14
Compare
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.
What's new in this PR
PR Submission Checklist for internal contributors
SQPIT-764feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.