-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Unify duplicate handling in Task
s
#2
Comments
Is there any task that should take and keep the first? Seems like it is always the last. Otherwise I really like your proposition! |
I think not. It should always be the last. |
Hey @soywod! Can you assign me this issue? |
Or make me a collaborator so I can do myself, how you prefer :D |
Or make me a collaborator so I can do myself
Invitation sent!
|
soywod
changed the title
feat: Unify duplicate handling in
Unify duplicate handling in Sep 10, 2024
Task
sTask
s
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
warn
ing`Append
-> LastPostAppendNoOp
-> Last (nowarn
ing)PostAppendCheck
-> Last (nowarn
ing)AuthenticateTask
-> Take last data (no warning). May take data instead of status.Proposal:
I think we want to tell our users not only that there was a duplicate, but also how we resolved the situation. Maybe something like ...
... ?
The text was updated successfully, but these errors were encountered: