Conversation
Remove a trailing slash in link which was causing redirect to a not found page.
* Upgrade gatsby-remark-code-repls * fix path issue on Windows Gatsby uses `slash` to normalize paths. Because of this `path.join` causes an issue on Windows
Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com>
…s (#866) Co-authored-by: Edgar Muentes <Edgar.Muentes@aexp.com> Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com>
Co-authored-by: 宋文强 <pwnn@users.noreply.github.com>
Co-authored-by: Eduard Poracký <eporacky@trionyx.sk> Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com>
Prefixed `unstable_` for the experimental ReactDOM.createRoot().
* Update blog post for RC1 * Update 2020-08-10-react-v17-rc.md
Disclaimer: I'm an organiser of React Summit, React Advanced London and React Day Berlin - changes proposed in this PR is a small effort to actualise the list of events next to updating our own event dates Next to updating own conference dates, I've made following changes: * Removed 2020 events that, based on the current information from their websites, are cancelled or postponed without a new date * Moved 2020 events that have actually ran to the "past events" section * Updated dates of some events in 2020 that have not announced their cancellation, but moved dates within this year What I didn't do: * I haven't added 2020 cancelled events with their assumed 2021 dates, as it's up to organizers to confirm those and re-add * To stay consistent with point above - I'm also not adding our (GitNation - React Summit, React Advanced) cancelled event dates that moved to 2021 * Conferences that have a past dates, but has not clear statement on the website about cancellation have not been removed, but rather moved to "past events" section The information is relevant as of today's date - during these hard times plans do change frequently, so some information may be outdated by the time this PR is merged. I'll be happy to provide amends until it's merged.
…… (#3159) * Updating the docs to reflect the fact that React.memo can be used with both class and functional components * removed misleading para
* Fix Navbar covering heading while using anchor in docs * reduced number of lines of code from 2 to 1 * Forgot to do tests before. Have done those now with no errors
Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com>
|
Deploy preview for uk-reactjs ready! Built with commit 512f1cd |
vldmrkl
approved these changes
Sep 22, 2020
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
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.
This PR was automatically generated.
Merge changes from reactjs.org at 1becaff
The following files have conflicts and may need new translations:
Please fix the conflicts by pushing new commits to this pull request, either by editing the files directly on GitHub or by checking out this branch.
DO NOT SQUASH MERGE THIS PULL REQUEST!
Doing so will "erase" the commits from master and cause them to show up as conflicts the next time we merge.