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.
Dependency updates
react-intl
: React Intl was the most problematic to upgrade.intlShape
was removed so we needed to create it again. Because of this we added a newutil/reactIntl.js
file. This file is now used to wrap all the react-intl related imports.addLocaleDate
function was removed and react-intl library is now relying on native Intl APIs: Intl.PluralRules and Intl.RelativeTimeFormat. In order to support older browsers we needed to addintl-pluralrules
andintl-relativetimeformat
toutil/polyfills.js
full-icu
which caused changes tostart
andtest
scripts in
package.json
. We also needed to add a specific config fornodemon
textComponent
inIntlProvider
changed toReact.Fragment
so we need to explicitlyset
textComponent
tospan
. Otherwise, all the snapshots would have changed and it mightaffect to UI if there are styles added to these spans generally in customization projects.
Note:
FormattedMessage
component now supportstagName
prop and improved rich-text formatting.Read more from Upgrade guide for [email protected]
Updated
react
,react-test-renderer
andreact-dom
to 16.9.0. After these updates oldlifecycle methods
componentWillMount
,componentWillUpdate
andcomponentWillUpdate
will cause deprecation warnings. Check the updated components from the PR #1172Migrate from
react-helmet
toreact-helmet-async
, since react-helmet wasn't updated oftenenough and
react-helmet-async
was supporting React 16+ better. This caused changes to app.js (<HelmetProvider>
added) and it changes the way how Helmet needs to be imported. #1179import Helmet from 'react-helmet';
vsimport { Helmet } from 'react-helmet-async';
sanitize.css
was moved to own file instead of importing it from npm package because updating it accidentally might break the UI.react-redux
: v5.1.1 -> v7.1.1 Note:connect
is now using Hooks.react-redux
uses internally.seedrandom
: v2.4.4 -> v3.0.3. (FTW wasn't affected.)inquirer
: v6.5.0 -> v7.0.0. (They dropped support for Node 6)final-form
,final-form-arrays
,react-final-form
andreact-final-form-arrays
. This forced us to make some code changes:format={null}
=> use identity function instead:format={v => v}
parse={null}
=> use identity function instead:parse={v => v}
input
keytype
attribute too.form
as a way to pass id/name of the form to the form. So, that if there's a need to add id's to inputs they could be unique${form}.inputId
. This was a bad choice since when we ended up using Final Form (and this newer version of it): they introducedform
prop of their own. That form prop is used to pass in formAPI - and if there's form prop passed outside of Final Form, it is used internally as an alternative formAPI. In v3.4.0, we have tried to rename all the remaining oldform
props asformId
.react-final-form
: 4.0.2 > v5.0.0 -> v6.0.0 -> v6.3.1react-dates
: v18.5.0 -> v20.3.0prettier
: v1.17.0 -> v1.18.2yarn run format
path-to-regexp
: v2.4.0 -> v3.0.0. It is used in create populated paths in our route generation.sharetribe-scripts
: v3.0.0 -> v3.1.1jsx-a11y/href-no-hash
for eslint reference since it didn't exist anymore:/* eslint-disable jsx-a11y/href-no-hash */
Sentry: v4.5.1 -> v5.6.2
Other changes
Update to German and French translations. #1184
Bug fixes to ProfileSettingsForm, EditListingAvailabilityForm, and FieldBirthdayInput
Lodash vulnerability: we enforced a newer version for
react-google-maps
andreact-dates
through package.json resolutions