Skip to content
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

feat: add redo to streaming payment #3648

Open
wants to merge 4 commits into
base: feat/streaming-payments-ui
Choose a base branch
from

Conversation

CzarekDryl
Copy link
Contributor

@CzarekDryl CzarekDryl commented Nov 6, 2024

Description

  • Changed kebab menu options for streaming payment

Testing

  • Install streaming payment extension
  • Create streaming payment action
  • In completed action screen open kebab menu
  • Check if redo action works fine

TODO

  • Add redo action to activity table

Resolves #3141

@CzarekDryl CzarekDryl self-assigned this Nov 6, 2024
@CzarekDryl CzarekDryl marked this pull request as ready for review November 13, 2024 10:18
@CzarekDryl CzarekDryl requested a review from a team as a code owner November 13, 2024 10:18
Copy link
Contributor

@iamsamgibbs iamsamgibbs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work on this! I tested every scenario with different start / end conditions I could think of and it is handling them all fine.

Screenshot 2024-11-13 at 14 40 47 Screenshot 2024-11-13 at 14 40 54

The only reason I'm rejecting, is because of this recent PR #3587 which re-enables the redo option from the activity table. Currently here it isn't possible to redo via the activity table. It would be great if the feat/streaming-payments-ui feature branch could be rebased onto master and make sure the redo via activity table functionality is working here. Especially as there is some custom logic in getting the correct values to show.

const isStartImmediately =
Math.abs(startTimeDate.getTime() - new Date(createdAt).getTime()) < 60000;

// console.log({isStartImmediately, startTimeDate, createdAt});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left over console log

Copy link
Contributor

@iamsamgibbs iamsamgibbs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Switching this to an approval and we can handle the redo via activity table as a separate issue after the branches have been rebased.

Copy link
Contributor

@bassgeta bassgeta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works nice and the solution is very simple 👍
Tried out a few cases, got 2 on video too 👀

redo-streaming-2024-11-22_15.26.57.mp4

@@ -42,6 +42,7 @@ const useActionFormBaseHook: UseActionFormBaseHook = ({
validationSchema,
actionType,
id,
transform,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice catch!

Copy link
Member

@rdig rdig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tested this but can only redo the streaming payment action from the sidebar menu, not from activity feed menu.

I believe redo-ing from the activity feed should also be included in this PR

From the sidebar:

Screenshot from 2024-11-22 18-24-51
Screenshot from 2024-11-22 18-25-53
image
Screenshot from 2024-11-22 18-26-39

From the activity feed:

Screenshot from 2024-11-22 18-27-00

@CzarekDryl
Copy link
Contributor Author

@rdig Can we make it in other PR? feat/streaming-payments branch needs to be rebased to have changes from #3587

@CzarekDryl CzarekDryl requested a review from rdig November 28, 2024 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants