-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Bump react-native-live-markdown (use worklets) #53627
Merged
luacmartins
merged 20 commits into
Expensify:main
from
s77rt:react-native-live-markdown-better-loose-url-website-regex
Dec 13, 2024
+81
−41
Merged
Changes from 11 commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
a9b0d1a
Bump react-native-live-markdown to 0.1.192
s77rt fe0e4ac
Merge branch 'Expensify:main' into react-native-live-markdown-better-…
s77rt 2bc34bb
worklets patch
s77rt fd3768d
patch html-entities
s77rt 23c0cfc
Merge branch 'Expensify:main' into react-native-live-markdown-better-…
s77rt 18d23a2
mock LiveMarkdownModule
s77rt b4a19c2
remove unused import
s77rt eb73197
better type for parseExpensiMark mock
s77rt ff3c095
fix lint
s77rt 02d1d08
removed duplicated line
s77rt 4a9bd7c
update react-native-live-markdown, expensify-common and react-native-…
s77rt 1717f7b
update react-native-live-markdown to 0.1.207
s77rt b1b764b
Merge branch 'Expensify:main' into react-native-live-markdown-better-…
s77rt 9dd7f4f
Delete patches/react-native-reanimated+3.16.4+001+hybrid-app.patch
s77rt 129ea27
Add back "Clean up deleted files" task
s77rt 0eb5bd5
Add back "Get common ancestor commit" task
s77rt 9a1b954
add comment to trigger git diff
s77rt bebb92a
Merge branch 'main' into react-native-live-markdown-better-loose-url-…
s77rt e9d088d
Merge branch 'main' into react-native-live-markdown-better-loose-url-…
AndrewGable adbd181
update patch index
luacmartins File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
import {MarkdownTextInput} from '@expensify/react-native-live-markdown'; | ||
import type {parseExpensiMark} from '@expensify/react-native-live-markdown'; | ||
|
||
global.jsi_setMarkdownRuntime = jest.fn(); | ||
global.jsi_registerMarkdownWorklet = jest.fn(); | ||
global.jsi_unregisterMarkdownWorklet = jest.fn(); | ||
|
||
const parseExpensiMarkMock: typeof parseExpensiMark = () => { | ||
'worklet'; | ||
|
||
return []; | ||
}; | ||
|
||
export {MarkdownTextInput, parseExpensiMarkMock as parseExpensiMark}; | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Is it okay if we have this mock here or should we move it to
react-native-live-markdown
somehow?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.
This part of the mock can be moved. But I'm not sure about the react-native part. Maybe we can just avoid throwing an error if NativeLiveMarkdownModule is not available? (same as it was before). The global.jsi_setMarkdownRuntime check is probably enough
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.
Raised PR Expensify/react-native-live-markdown#578.
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.
Thanks for the PR! Left couple of comments there.
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.
Do I need to wait for the above PR to be completed, and then start testing this PR?
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.
Yes, let's wait for that PR with the mock. I've asked my collegaues to review that PR (it looks good for me, just wanted another pair of eyes on it). I hope we can merge that PR today. Then we can bump here and ask for QA.
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.
@s77rt I've just merged the PR introducing the mock to
react-native-live-markdown
(Expensify/react-native-live-markdown#578). Let's bump live-markdown to 0.1.207, remove mock in this PR and we should be ready to test.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.
Done! This is ready for test