docs: work around issue with docs.page codeblocks #637
Conversation
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
|
To view this pull requests documentation preview, visit the following URL: docs.page/invertase/react-native-google-mobile-ads~637 Documentation is deployed and generated using docs.page. |
|
The page seems to be working fine again. |
Correct, the issue has been resolved upstream. No need for the work around anymore 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Our docs for impression-level ad revenue are currently down. They used to work perfectly but stopped working a few days ago. I suspect the recent major docs.page update.
The page currently returns status 500. Through trial and error, I narrowed the issue down to the two code blocks on that page. The page fails to render when the codeblocks use
tsas their language. Curiously enough, changing the language totsxresolves the issue.I just reported the issue upstream: invertase/docs.page#364
If we don't want to wait for it to get addressed, we can switch the affected code blocks to
tsx.Test Plan