-
Notifications
You must be signed in to change notification settings - Fork 57
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
Slash-commands now look for exact match #142
Conversation
Hello @jrepe, Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here. Per the Mattermost Contribution Guide, we need to add you to the list of approved contributors for the Mattermost project. Please help complete the Mattermost contribution license agreement? This is a standard procedure for many open source projects. Please let us know if you have any questions. We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team. |
/check-cla |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nicely done :) Would you mind adding a test for this particular code change?
Of course, will do 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will kinda miss the regex there, but I agree that it was probably more confusing in partial match situations.
LGTM
This PR has been automatically labelled "stale" because it hasn't had recent activity. |
@DHaussermann kind reminder to help with reviews, thank you! |
Hey @jrepe thank you so much for fixing this issue! This bug was especially annoying. I've done some testing and the issue is fixed but, I did find a small issue introduced by this solution. In cases where you're using With this change, it will not pull them back as list must now be an exact match. I have tested this with all of the commands and it solves the issue for manipulating the data. But, would it be possible to make an exception for |
Hey, thanks for the comment, I'll look into it. I imagined that this might have some consequences somewhere else that would be undesirable. Sorry for the delay though, I've had little time lately, but will get on this as soon as I can. |
This PR has been automatically labelled "stale" because it hasn't had recent activity. |
How's it going, @jrepe? Sounds like you have been busy, but I just wanted to check in to see if you have any further questions or need any assistance? |
Summary
The pull request fixes the issue where
/autolink [command]
doesn't look for exact match when manipulating links.However, the current implementation might be too naive, because it'll affect all commands and not just those that manipulate links, so I'd appreciate feedback if that is desirable or not, otherwise I'll need to give more thought to how to fix this only for specific commands.
Ticket Link
Fixes #138