Release/18.0.0 #781
Merged
Release/18.0.0 #781
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
* [JSS] Disallow file deploy for Next.js solutions * Use `sitecoreDistPath` property
* Prep for 'jss create' template customizations: * Pull Rest/GraphQLDictionary/LayoutService creation out of page-props-factory to separate factories for each (REST by default). * Move the [[..path]].SSR.tsx alongside default (SSG) one under /pages * Added --fetchMode and --renderMode 'jss create' parameters to nextjs template * fixed formatting * Use "enum" for Fetch/RenderMode * Parameters renamed: "fetchMode" > "fetchWith", "renderMode" > "prerender" Co-authored-by: Adam Brauer <adab@sitecore.net>
* remove the need for the server-wrapper * remove webpack config * Create valid bundle * Add empty line * Add empty line * Remove 'exclude' option * Change doc related to angular bundles Co-authored-by: Erik van 't Klooster <ao491769@achmea.nl>
* [sitecore-jss] Add GraphQLLayoutService * Change jsdoc * add changes * Use latest schema * Optional cahining for `data` * Add ability to use custom search query * remove param * Provide ability to format only query arguments instead of modifying response data
This includes the new docs pages written since the 16.0.0 release and the deployment fixes that were done as part of the 16.0.0 release ------------------------------------------ * push lock's * revert package.json * v16.0.0 * Revert lockfileVersion on master (#610) * Revert "push lock's" This reverts commit e951cc4. # Conflicts: # packages/sitecore-jss-angular-schematics/package-lock.json # packages/sitecore-jss-angular/package-lock.json # packages/sitecore-jss-cli/package-lock.json # packages/sitecore-jss-dev-tools/package-lock.json # packages/sitecore-jss-forms/package-lock.json # packages/sitecore-jss-manifest/package-lock.json # packages/sitecore-jss-nextjs/package-lock.json # packages/sitecore-jss-proxy/package-lock.json # packages/sitecore-jss-react-forms/package-lock.json # packages/sitecore-jss-react-native/package-lock.json # packages/sitecore-jss-react/package-lock.json # packages/sitecore-jss-rendering-host/package-lock.json # packages/sitecore-jss-tracking/package-lock.json # packages/sitecore-jss-update-package/package-lock.json # packages/sitecore-jss-vue/package-lock.json # packages/sitecore-jss/package-lock.json # packages/sitecore-pipelines/package-lock.json # samples/angular/package-lock.json # samples/nextjs/package-lock.json # samples/node-headless-ssr-proxy/package-lock.json # samples/react-native/package-lock.json # samples/react/package-lock.json # samples/sitecore-embedded-jss-app/package-lock.json # samples/sitecore-javascript-renderings/package-lock.json # samples/vue/package-lock.json * addl lock updates from lerna reset Co-authored-by: Adam Brauer <adab@sitecore.net> * [Doc] [NextJs] Node extra CA certificates configuration (#612) * Doc: Configure Sitecore CA certificates for Node.js * Cross-link / consolidate on walkthrough-dotnetnew * Cross-links from headless mode docs * Fix minor lang issues * Format UI labels, add emphasis Co-authored-by: Adam Brauer <adab@sitecore.net> Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com> * [Doc] [NextJS] Error routes (#611) * [Doc] [NextJS] Error routes * Update en.md * Add improvements * Fix punctuation Co-authored-by: Anastasiya Flynn <flynn.github@gmail.com> Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com> * [Docs] Troubleshooting page (#613) * [Docs] Troubleshooting page * Add lang review * PR review improvements * Doc wording consistency Co-authored-by: Adam Brauer <400763+ambrauer@users.noreply.github.com> * Apply house style rule (where -> what) We always tell WHERE the user is to do things, then WHAT to do. * Address language and style issues * Edit 'troubleshooting' page Improve clarity per PR comments, add a note for checking sitecore config values, remove blurry image. * Review language & style * Fix hard to read sentence * Encode ..., escape [] Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com> Co-authored-by: Adam Brauer <400763+ambrauer@users.noreply.github.com> * [Docs] [NextJs] Experience Editor Integration Architecture and APIs (#616) * EE integration architecture and APIs doc Co-authored-by: Adam Brauer <adab@sitecore.net> Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com> * Fix typo (#621) * [Docs][NextJS] Extract Next.js telemetry info into new page (#615) * Extract Next.js telemetry info into new page * Update navigation * [Doc] [NextJS] Error routes (#611) * [Doc] [NextJS] Error routes * Update en.md * Add improvements * Fix punctuation Co-authored-by: Anastasiya Flynn <flynn.github@gmail.com> Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com> * Fix route name Co-authored-by: Illia Kovalenko <23364749+illiakovalenko@users.noreply.github.com> Co-authored-by: Anastasiya Flynn <flynn.github@gmail.com> Co-authored-by: Adam Brauer <400763+ambrauer@users.noreply.github.com> * typo iterfaces -> interfaces (#600) Co-authored-by: Adam Brauer <400763+ambrauer@users.noreply.github.com> * Fix heading in note box (#622) * Nav updates for new troubleshooting pages (#623) Co-authored-by: Adam Brauer <adab@sitecore.net> * Merge branch 'master' from heroku remote into updates-from-master # Conflicts: # lerna.json # packages/sitecore-jss-angular-schematics/package-lock.json # packages/sitecore-jss-angular-schematics/package.json # packages/sitecore-jss-angular/package-lock.json # packages/sitecore-jss-angular/package.json # packages/sitecore-jss-cli/package-lock.json # packages/sitecore-jss-cli/package.json # packages/sitecore-jss-dev-tools/package-lock.json # packages/sitecore-jss-dev-tools/package.json # packages/sitecore-jss-forms/package-lock.json # packages/sitecore-jss-forms/package.json # packages/sitecore-jss-manifest/package-lock.json # packages/sitecore-jss-manifest/package.json # packages/sitecore-jss-nextjs/package-lock.json # packages/sitecore-jss-nextjs/package.json # packages/sitecore-jss-proxy/package-lock.json # packages/sitecore-jss-proxy/package.json # packages/sitecore-jss-react-forms/package-lock.json # packages/sitecore-jss-react-forms/package.json # packages/sitecore-jss-react-native/package-lock.json # packages/sitecore-jss-react-native/package.json # packages/sitecore-jss-react/package-lock.json # packages/sitecore-jss-react/package.json # packages/sitecore-jss-rendering-host/package-lock.json # packages/sitecore-jss-rendering-host/package.json # packages/sitecore-jss-tracking/package-lock.json # packages/sitecore-jss-tracking/package.json # packages/sitecore-jss-update-package/package-lock.json # packages/sitecore-jss-update-package/package.json # packages/sitecore-jss-vue/package-lock.json # packages/sitecore-jss-vue/package.json # packages/sitecore-jss/package-lock.json # packages/sitecore-jss/package.json # packages/sitecore-pipelines/package-lock.json # packages/sitecore-pipelines/package.json # samples/angular/package-lock.json # samples/angular/package.json # samples/nextjs/package-lock.json # samples/nextjs/package.json # samples/node-headless-ssr-proxy/package-lock.json # samples/node-headless-ssr-proxy/package.json # samples/react-native/package-lock.json # samples/react-native/package.json # samples/react/package-lock.json # samples/react/package.json # samples/sitecore-embedded-jss-app/package-lock.json # samples/sitecore-embedded-jss-app/package.json # samples/sitecore-javascript-renderings/package-lock.json # samples/sitecore-javascript-renderings/package.json # samples/vue/package-lock.json # samples/vue/package.json * origin and heroku remotes has difference app roots, so these changes are supposed to be on docs/package.json Co-authored-by: illiakovalenko <iki@sitecore.net> Co-authored-by: illiakovalenko <zlatoborodyi@gmail.com> Co-authored-by: Adam Brauer <400763+ambrauer@users.noreply.github.com> Co-authored-by: Adam Brauer <adab@sitecore.net> Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com> Co-authored-by: Illia Kovalenko <23364749+illiakovalenko@users.noreply.github.com> Co-authored-by: Calvin Williams <40271790+sc-CalvinWilliams@users.noreply.github.com>
* Add changes * add changes * Fix issues * update packages * Push package-lock * Add release note * update react-native svg in sitecore-jss-react-native * Updated env setup doc link / tab name * Fix component params example for connected mode - all params will come in as string from layout service * Fix image sample 'src' prop type for disconnected - this will be number in disconnected, string in connected * Fixed tunnel for use of secure (https) Sitecore endpoints. Updated to latest ngrok. * Release note updates * Added height / width to plain image example (these are required for network images i.e. connected mode). Removed srcSet / adaptive image example since it's not supported. Co-authored-by: Adam Brauer <adab@sitecore.net>
* Dependency audit - root: Removed metro, updated ini * Dependency audit - package updates (all semver-compatible, only low remaining) * Dependency audit - nextjs sample * Dependency audit - react, sitecore-embedded-jss-app, sitecore-javascript-renderings, vue samples * Dependency audit - e2e * lock file updates Co-authored-by: Adam Brauer <adab@sitecore.net>
…ion options for 'jss create' (#620) * Progress on doc updates for SSG/SSR & REST/GraphQL app modes * parameter rename * Another batch of updates * Added 'Switching between REST and GraphQL' doc, minor cleanup * Update "Tracking & Analytics Overview and Architecture" docs Explicitly state that SSR is required for personalization, to avoid confusion * Add jss create to CLI reference docs * Add reference to CLI doc * Added clarification to analytics support (SSR with Sitecore Layout Service REST API only) to "How is Next.js Different" doc * Provide more detailed example for `jss create` with optional params * Concentrate REST & SSR info in a pre-requisites section & clean up * Re-work intro, adjust heading levels * Drop parens * Change wording * Add CLI reference link, add headings for the switch sections * Change case for consistency * Add note about visitor consent for tracking * Change heading Co-authored-by: Adam Brauer <adab@sitecore.net> Co-authored-by: Anastasiya Flynn <flynn.github@gmail.com> Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com>
Create new GraphQL-based dictionary service implementation in sitecore-jss GraphQLDictionaryService (implements DictionaryService interface) using the layout query to get site root item using the search query to get all dictionary phrases in the site (by template) accounting for search query pagination RestDictionaryService and RestDictionaryService inherit common functionality from new abstract class DictionaryService This branch also has refactoring to organize our services classes better (not that we have more of them) and to make files in sitecore-jss follow consistent naming conventions. Renamed classes: LayoutService -> RestLayoutService LayoutServiceInstanceConfig -> RestLayoutServiceConfig DictionaryService -> RestDictionaryService DictionaryServiceConfig -> RestDictionaryServiceConfig DictionaryServiceData -> RestDictionaryServiceData (and removed from export since it's not used in the sample apps) HtmlJsonFetcher -> HtmlDataFetcher (renamed because the return type is arbitrary and not guaranteed to be JSON) New classes: GraphQLLayoutService, GraphQLLayoutServiceConfig ---------------- * Create utils/routingUtils.ts Move query string formatting out of the dataApi file, and into a general routing util fil since it can be used by other APIs too. * Combine util functions into a common namespace Now all util functions are available from the 'util' module exported from sitecore-jss * extract getUrl * Standardize file naming in sitecore-jss * Standardize file naming in sitecore-jss * Everything in the 'data-fetcher' module is coupled to Axios, so lets rename it to 'axios-fetcher' and use 'data-fetcher' for the underlying generic interface * Everything in the 'data-fetcher' module is coupled to Axios, so lets rename it to 'axios-fetcher' and use 'data-fetcher' for the underlying generic interface * Rename type HttpJsonFetcher -> HttpDataFetcher This is a generic type, so there is no guarantee that the result is JSON. The result can be any type. * Rename the sample app's data-fetcher to data-fetcher-factory to better describe what it's doing and to make it consistent with our other files * whitespace and todo for later * Rebase with dev and move some of the refactoring to a separate branch * TODOs for later * This is left-over from the refactoring that moved to another branch * GraphQLDictionaryService implementation * Add pagination and error handling to GraphQL Dictionary service; split the 2 dictionary services into separate files; create base class for dictionary services to share code * Update graphql-request-client - remove private passthrough function that isn't needed; add error handling * Add caching to graphql dictionary service * linting * Give name/date context to TODOs So we know who to bug 😸 * Update references to renamed exports * Use lower case for GUIDs * Show more data in graphql client errors * Ignore *.eslintcache * GraphQL dictionary service now fetches the root item ID, so it does not have to be provided explicitly * lint * unit tests * Undo accidental commit * Use Object.freeze on dictionary service constants * Rename DictionaryService methods - getCacheValue and setCacheValue * Add doc comments to GraphQLDictionaryServiceConfig * GraphQLDictionaryService - extract default pageSize into 'defaults' object * Rename graphql.dictionary-service to graphql-dictionary-service. Rename rest.dictionary-service to rest-dictionary-service. * Rethrow error from promise chain in graphql-request-client * Improve comments in data-fetcher.ts * Comments * lint * fetchDictionaryData - do not use make return value depend on cache * Revent renaming of src\lib\data-fetcher.ts * Update comments and variable name * jssAppTemplateId should be a required variable in the getRoot query * capitalize DEFAULTS object name * Rename appName -> siteName
* changes * update to 11.2.6 * Fix angular schematics * Update apollo client * Upgrade typescript-eslint * upgrade angular-eslint * update packages * upgrade test packages * Update sitecore-jss-angular packages * Upgrade angular-devkit * FIx error: JssModule can't read property 'emod' of undefined * Add chalk, fix deprecations * Push lock files * Remove deprecated extractCss * Release notes * Fix typo * Fix ini (low severity) vulnerability * Edit release-notes Co-authored-by: Adam Brauer <adab@sitecore.net>
* Added 'sc_apikey' header authentication for GraphQL layout and dictionary services * Added sc_apikey header / param to GraphQL sitemap service. Started sample app updates. * Fixed siteRootQuery error: Variable "$language" of type "String" used in position expecting type "String!" * Generate environment variables for computed config values as well * Added GRAPH_QL_ENDPOINT to .env file and Vercel deployment doc * PR feedback: use endpoint const, get rid of "calculated config" verbiage * Removed prettier comment * PR feedback: removed "Edge" usage for XM references Co-authored-by: Adam Brauer <adab@sitecore.net>
…from Experience Edge (#628) * Push first changes * commit * push files * Exclude sample from e2e * push package-lock * update readme.md * Update readme * update config * update * refactoring * Add changes * Remove rewrite_exclude_urls * Added API_KEY * add todo for testing of graphql queries * Change validation message * Change canary version * Push package-lock * Add changes after review * Update pre-requisite * Update canary build * Add changes related to sc_apikey header * Update config apiKey description * Update sc_apikey header description * Update canary version * Push lock files * Fix UT
[Docs] Change starter->sample and associated changes + small lang & style fixes
[445596][Docs] Replace jss.sitecore.net with jss.sitecore.com
* Add video walkthrough * Update iframe src with correct embed url Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com>
…tures (#632) * Update with samples entry for Next.js and highlight features * Update product name * Drop mention of create-next-app * Fix small grammar issues * Update README.md Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com>
…722) * Update Next.js sample config - layoutServiceConfiguration="default" * Update samples/nextjs/sitecore/config/JssNextWeb.config Co-authored-by: Adam Brauer <400763+ambrauer@users.noreply.github.com> Co-authored-by: Adam Brauer <400763+ambrauer@users.noreply.github.com>
Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com>
* Move video demonstration for better fit * Add link to Edge docs * Add Edge alternative to publish:end hook config * Add link to API provisioning docs for Edge * Add Sitecore XM detail to publish:end webhook Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com>
…49] (#741) * Fix step for deploying Next.js items to Sitecore * Clarify how to deploy a Next.js app to Sitecore * Push hash to history if present, account for target other than link * Handle hash when routing * Add flags docs/data/routes/docs/nextjs/getting-started-nextjs/walkthrough-jsscreate/en.md Co-authored-by: Adam Brauer <400763+ambrauer@users.noreply.github.com> Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com> Co-authored-by: Adam Brauer <400763+ambrauer@users.noreply.github.com>
* Separate content and move getStaticPaths Moves getStaticPaths documentation under "Page Routing". Redirects from old to new location. Fixes cross-references. Removes GraphQLSitemapService which should go in its own doc. * Add nav and page for GraphQLSitemapService * Add EXPORT_MODE variable to steps * Use ManifestInstance * Update deprecated signature * Update doc title * Link to first mention * [483268] Document graphQL query error for Next.js + SXA * Update GraphQLSitemapService documentation * Update navigation item * Add Services & APIs overview for fundamentals * Split back- and front-end layout service, update content Splits the Layout Service section into the front- and back-end parts for easier management of changes. Updates nav. Adds redirects as needed. * Fix typos * Add link to Next.js app lib as example of service factories * Clarify in the heading this is the REST layout service * Revert move of getStaticPaths topic * Make example framework agnostic * Remove duplicate heading * Fix typo * Remove mystery variable * Re-word factory description * Clarify JSS clients interact with Sitecore Headless services These types of distinctions become increasingly important as we separate server components from JSS services * Reorganize Layout overview * Add redirect to overview for Layout service Since server components Layout service and JSS one were mixed in a single doc, we don't know which one old links out in the world were meant to reach. By pointing at the overview, devs can then pick the one they are interested in. * Refactor Dictionary service docs Split Sitecore from JSS Add redirects Update nav * Update title * Fix indentation * Specify other services/apis * Fix redirect for layout service landing * Update layout service links * Remove dataApi reference * Expand description and provide GraphQL examples for Dictionary service * Clean up Headless Dictionary Service description * Expand description and provide GraphQL example for Layout service * Update links to dictionary service documentation * Enrich dictionary overview with info about GQL and links * Incorporate doc update from PR#744 * Remove duplicate menu item * Update docs/data/routes/docs/fundamentals/services/dictionary/overview/en.md Adds missing comma Co-authored-by: Anastasiya Flynn <flynn.github@gmail.com> * Move Services higher in the navigation * Change tone * Improve clarity of data fetching options * Change endpoint / product order to match bullet points * Specify the package that provides the dictionary API * Elaborate JSS Dictionary API description * Add note on sample app * Get personal * Remove obscure references to back-end concepts * Add returned data example * Change "route data" to "layout data" + small language changes * Link to query definition in branch src file * Re-arrange some content * Specify name for Edge Preview endpoint and add original gql endpoint * Add missing empty line between heading and quote * Clarify that the tracking parameter is only intended for Sitecore XP * [487542] Clarify required version of Sitecore and Headless Service for Next * [486092] Update troubleshooting: Next.js app does not render on Vercel Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com> Co-authored-by: Anastasiya Flynn <flynn.github@gmail.com>
* Generate ref docs for jss and nextjs sdks * Regenerate docs with updated readmes * Update readmes and location of ref-docs * Generate ref-docs without duplicating package readme Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com>
Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com>
Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com>
Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com>
* Update release notes for v18. Create CHANGELOG file. * Add link to Sitecore Experience Edge schema docs * Link to JSS Layout / Dictionary APIs * Add link to sitecore-jss and sitecore-jss-nextjs ref docs * Fix Edge heading and add link to docs * Add section on docs and update links * Drop "API" * Wrap param names in backticks * Add link to CLI docs for create * Improve links to Edge docs sections The Edge docs were published today so we now have access to section IDs * Update links to Sitecore docs Co-authored-by: Anca Emcken <AncaIO@users.noreply.github.com>
…stead of master (#780)
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/sitecore-jss/edge-e2e-styleguide/5XniypbG7p8zrEEejepi17LrcFbz |
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.
JSS 18.0.0 Release Notes
Breaking changes
[sitecore-jss-react-native]RemoveddataConversation, sinceeditableproperty not used indisconnectedmode. (#624)[samples/angular]Upgradeangularto v11. (#635)[samples/nextjs]Change how a custom query can be used in GraphQLSitemapService. Previous way: pass aformatSearchQueryfunction tofetchExportSitemaporfetchSSGSitemap. New way: extend theGraphQLSitemapServiceclass and override thefetchSitemapmethod. (#638)With the added support of GraphQL endpoints, the API surface area of JSS has essentially doubled. As a result, some reorganizing was done in the base packages, which causes breaking changes for how some services, classes and functions are exported. If you have imports from JSS base packages in your project, they may need to be updated per the migration guide table.
Introducing support for Sitecore Experience Edge 🎉🎉🎉
Experience Edge is Sitecore's new delivery platform, which serves Sitecore data to your JSS app at blazing fast speeds. You should learn about the Experience Edge GraphQL schema.
[samples/nextjs]IncludeServerUrlInMediaUrls"default" configuration to avoid exposing the Sitecore server publicly when using Experience Edge.[react][angular]and[vue]samples can also utilize Sitecore Experience Edge. A new[node-headless-ssr-experience-edge]sample has been adeded to demonstrate how to configure this. Read docs.New Documentation
We have added & polished documentation for our main package and our Next.js SDK, as follows:
For
sitecore-jss, see:For
sitecore-jss-nextjs, see:New & Improved Service Classes
Read our updated docs:
[sitecore-jss]GraphQLDictionaryServiceis a new service for fetching dictionary data using GraphQL Read docs.GraphQLLayoutServiceis a new service for fetching layout data using GraphQL Read docs.[sitecore-jss-nextjs]GraphQLSitemapServiceeasier to customize by allowing overrides of default options. (#682, #705)Other Notable Improvements
[sitecore-jss]Enable debug logging for JSS services using the debug module. Read docs.jss createcommand. Read docs.[samples/react-native](#624)<Layout/>component in order to have shared navigation panel.dataConversation.Bug Fixes
[sitecore-jss]mediaApi.updateImageUrlnow only switches to JSS media handler prefix ifimageParamsare sent. Otherwise, the original media URL is returned. Fixes hash errors ("ERROR MediaRequestProtection: An invalid/missing hash value was encountered.") from appearing in Sitecore logs ([sitecore-jss] [mediaApi]updateImageUrlfix for invalid hash errors on Sitecore #681)[samples/nextjs][samples/react][samples/vue]jss scaffoldgenerated files with inconsistent line endings ([JSS] [Samples] Scaffold component uses incorrect line endings #684)[sitecore-jss-nextjs]getStaticPathsonly pre-rendering the first 10 pages (638)[sitecore-jss-react]Render value instead of array of single value when value doesn't contain line breaks (714)[sitecore-jss-react-native](#624)styletype forSvgUrIinstead of Array.<HtmlView/>ifeditableis provided.[samples/react-native](#624)srcprop type in disconnected mode. Fix 'Plain image' example in connected mode. Remove unsupported 'Srcset image' adaptive example.paramsprop types in connected mode.[samples/node-headless-ssr-proxy]Fix how header value for 'accept-encoding' is set. This resolves an issue in the Angular sample where the /graphql page caused a console error (#680)[sitecore-jss-forms]Fix issue where pre-filled (default) form data isn't removed for multi-valued fields when user de-selects values (#677)