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

[MM-380] Fix issue of todo permalink opening in new tab #251

Merged
merged 5 commits into from
Jul 23, 2024

Conversation

ayusht2810
Copy link
Contributor

Summary

Fixed issue of todo permalink opening in new tab

Demo

screen-capture.3.webm

Ticket Link

Fixes #164

What to test?

  • Create a todo from a post
  • Check for the permalink created in RHS, which should open in the same tab
  • Create and assign a permalink to another user
  • The todo's permalink assigned to another user should also open in the same tab
  • Similarly, test for other actions like rejecting/accepting/completing a todo

@ayusht2810 ayusht2810 requested a review from mickmister as a code owner April 15, 2024 13:12
@ayusht2810 ayusht2810 self-assigned this Apr 15, 2024
@ayusht2810 ayusht2810 added the 2: Dev Review Requires review by a core committer label Apr 15, 2024
Copy link
Contributor

@mickmister mickmister left a comment

Choose a reason for hiding this comment

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

Great work 👍 Just a few comments

webapp/src/components/todo_item/todo_item.jsx Outdated Show resolved Hide resolved
server/command.go Outdated Show resolved Hide resolved
}

receiverIssue := newIssue(issue.Message, issue.Description, issue.PostID)
receiverIssue := newIssue(issue.Message, issue.PostPermalink, issue.Description, issue.PostID)
Copy link
Contributor

Choose a reason for hiding this comment

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

Seems like this could just accept a issue instead of these 4 fields derived from the issue

Copy link
Contributor Author

Choose a reason for hiding this comment

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

"type": "custom_todo",
"message": message,
"todo": todo,
"postPermalink": postPermalink,
Copy link
Contributor

Choose a reason for hiding this comment

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

What happens for posts that do not have this prop?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If we don't have this prop, we won't have a permalink in the message in the todo sent to other user in the post

@ayusht2810 ayusht2810 requested a review from mickmister April 24, 2024 10:54
@ayusht2810 ayusht2810 added the 3: QA Review Requires review by a QA tester label Apr 26, 2024
@mickmister mickmister removed the 2: Dev Review Requires review by a core committer label May 23, 2024
Copy link

@AayushChaudhary0001 AayushChaudhary0001 left a comment

Choose a reason for hiding this comment

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

This PR was tested and I found an issue in its functionality

Steps to reproduce:-

  1. Create any todo through a post in a channel.
  2. Once the Todo is reflected in RHS and is ready to be created, click spacebar against the name of the todo, it will create 2 permalinks.
  3. Click on the bottom permalink.

The permalink present in the bottom will not redirect you to a new page, instead the user will remain on the same page.

image (8)

cc: @mickmister

@Kshitij-Katiyar
Copy link
Contributor

Kshitij-Katiyar commented Jul 9, 2024

@AayushChaudhary0001 I have fixed the issue reported. Please have a look.
CC: @mickmister , @wiggin77

Copy link

@AayushChaudhary0001 AayushChaudhary0001 left a comment

Choose a reason for hiding this comment

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

@raghavaggarwal2308 The above PR has been re-tested and the above issue has been resolved. Approving this PR, LGTM.

@raghavaggarwal2308 raghavaggarwal2308 merged commit f25dc91 into master Jul 23, 2024
4 checks passed
@raghavaggarwal2308 raghavaggarwal2308 deleted the MM-380 branch July 23, 2024 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3: QA Review Requires review by a QA tester
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Permalink in a ToDo open in a new browser tab
5 participants