Closed dudanogueira closed 1 year ago
Hello @dudanogueira, hope you're doing well! 😄
I am passionate to work on this issue, if you can tell me, how should I go about the new fuselage message-parser
, I would be more than grateful to you.
Hello @dudanogueira, hope you're doing well! 😄 I am passionate to work on this issue, if you can tell me, how should I go about the new fuselage
message-parser
, I would be more than grateful to you.
Hi! Thanks! I will ask one of our developers as I don't know about it too, hehehehe
Thank you so much, I made a body parser for Our Github App using Regex, here https://github.com/RocketChat/Apps.Github22/pull/32 This one also seems fun to work on, I would be more than happy to contribute to this! 🚀🚀🚀
Oh, it seems that there is an assigned developer for this issue. @dudanogueira Should I notify that I'm working on an issue before creating PR?
P.S. Review https://github.com/RocketChat/Rocket.Chat/pull/27368
Hey @xareyli,
I was researching this issue, came to both before
and after
message save callback chains, and was thinking of changing something in the message parser, but your solution of reversing the beforeSaveMessage
callback chain seems super awesome!!! 😍😍
It would be awesome if you practice making a draft PR whenever you think of working on an issue, notifying other devs that you're working on the same.
thanks @xareyli and @henit-chobisa for the interest! I asked already our devs to review this PR!
Really appreciate it :)
Pleasure to work @dudanogueira, Every line of RC teaches something! 🤩
Description:
When you set up bad words to be filtered, it will change for *** on notifications, but not on channel.
Steps to reproduce:
WORKSPACE > SETTINGS > MESSAGE > Allow Message bad words filtering
WORKSPACE > SETTINGS > MESSAGE > Add Bad Words to the Blacklist
to onebadword,otherbadwordExpected behavior (this is what happens if using legacy message parser):
Actual behavior:
Server Setup Information:
Client Setup Information
Additional context
Relevant logs: