-
Notifications
You must be signed in to change notification settings - Fork 136
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
Modify mention user and mention report extras field names in ExpensiMark htmlToText and htmlToMarkdown rules #708
Conversation
Signed-off-by: Tsaqif <[email protected]>
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
Signed-off-by: Tsaqif <[email protected]>
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.
lib/ExpensiMark.js
Outdated
return `@${extras.accountIdToName[g1]}`; | ||
return `@${accountToNameMap[g1]}`; | ||
} | ||
return Str.removeSMSDomain(g2) |
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.
What's the purpose of these changes?
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.
+1
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.
The failling tests are because I didn't changes the fields in the test files yet, I am sorry.
For accountToNameMap
, I am following the pattern in the file for reportToNameMap
:
expensify-common/lib/ExpensiMark.js
Line 545 in 321e4a7
return reportToNameMap[g1]; |
accountToNameMap
is just a variable that store extras.accountIdToName
. It is the same thing:
expensify-common/lib/ExpensiMark.js
Line 481 in 321e4a7
const accountToNameMap = extras.accountIdToName; |
Should I revert it?
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 think we can revert it.
Signed-off-by: Tsaqif <[email protected]>
@mollfpr The failling tests are because I didn't changes the fields in the test files yet, I am sorry. Should be fine now... |
Signed-off-by: Tsaqif <[email protected]>
Signed-off-by: Tsaqif <[email protected]>
@mollfpr I have reverted the changes. |
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.
LGTM 👍
🚀Published to npm in v2.0.3 |
This PR changes field name of extras in ExpensiMark to fix type check fails.
Modify mention user and mention report extras field names in ExpensiMark htmlToText and htmlToMarkdown rules
Fixed Issues
$ Expensify/App#40928
Tests
What unit/integration tests cover your change? What autoQA tests cover your change?
typecheck on expensify/App should run successfully
What tests did you perform that validates your changed worked?
I have tested it on my other PR, thread report from report action that contains mention room and mention user should display report name properly in header report and in LHN.
QA
What does QA need to do to validate your changes?
N/A
What areas to they need to test for regressions?
N/A