Release/19.0.0 #849
Merged
Release/19.0.0 #849
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
Build context object in [[...path]] instead of in Layout, since the former is aware of whether route is null or not
* whitespace * rebase onto dev * Add pagination to sitemap service * improve comments * Add more error handling to graphql-sitemape-service * unit tests & lint * Release notes * Improve comments and type checking * Fix merge issues * Change visibility of GraphQLSitemapService.fetch to protected
* Low-level http request/response debug logging ("sitecore-jss:http" namespace) for both GraphQL (`graphql-request-client.ts`) and REST/fetch (`axios-fetcher`). Feature-level logging for dictionary and layout ("sitecore-jss:dictionary" and "sitecore-jss:layout" namespaces).
* Debug log tests for http logging
* Use object formatting, Axios 'toJSON' if available for errors
* Sitemap and experience editor feature-level logging
* Add rootItemId.toLowerCase() back to GraphQL sitemap query
* Added documentation
* Added to release notes
* PR feedback: SDKs > npm packages, added note about server-side only logs
* PR feedback: Centralized debug 'debuggers' in sitecore-jss
* Allow debugger injection into low-level http wrappers (axios-fetcher and graphql-request-client) so that these request/response logs can appear under feature-level namespaces.
* Updated docs
* Fix lint error
…itecore-jss:editing"
… releases (#634) * Update params, include example for specific release version * Add version compatibility info Include links to the compatibility table and to the CLI reference (updated with an example for creating an app using a previous version of JSS). * Fix typo * Add version compatibility note and link to table * Add compatibility note * Add note on Sitecore and JSS versions * Change versioning wording
…648) * Removed GraphQLFragmentTypes.json and corresponding script to generate. This is no longer needed with our removal of Apollo in the sample app. Also, added apikey to the introspection fetch and switched to use our GraphQLRequestClient as opposed to cross-fetch. * Updates for item children GraphQL edge schema change (now uses item search results pattern vs an array of items).
… line) to %O (pretty-print multiple line) formatting (#649)
* 'url-parse' dependency removal / upgrade to address vulnerability with v1.4.7 (https://nvd.nist.gov/vuln/detail/CVE-2021-27515) * Address y18n vulnerability (high): https://www.npmjs.com/advisories/1654 * lock file updates (npm run reset) * Remove url-parse from sitecore-jss-angular, remove @types from sitecore-jss-forms * Push lock files Co-authored-by: illiakovalenko <[email protected]>
…: Using next export` (#658)
Removed checklist
Combined description and motivation sections. Reworded Testing section title
Coby pear patch 1
…loaded twice (#659) * Fix internal links initialization * Add doc
* Refactoring - avoid duplicating getQueryString and other URL resolving logic; add unit tests for this function * Reorganize modules related to layout service - move them into their own folder and separate rest/graphql, similar to what we did with dictionary modules * remove 'data-api' file to improve the dependency hierarchy * Use proper querystring types from @types/node/querystring * break up util functions - isolate EE utils in 'experience-editor' file; break out logic for resolving app root into its own util for reuse in sitemap * Move test data for unit tests into a separate json file * Update properties in sitecore-jss/package.json * Enable syntax highlighting on graphql string via prettier * set noUnusedLocals to true in sitecore-jss-nextjs Co-authored-by: Adam Brauer <[email protected]>
* Fit error about missing http module - apparently importing and then exporting a lib in this manner is not ok * Fix circular dependency in src/utils/experience-editor * Add index/ts file under /i18n for easier imports * Add a table comparing API of sitecore-jss 16.0 vs 18.0 to migration guide and fix a couple missing exports
…lse</IncludeServerUrlInMediaUrls>. This should only be disabled for Next.js and SSR Proxy. (#802)
* Fix update-graphql-fragment-data react sample * Fix vue graphql:update * Fix angular graphql:update Co-authored-by: Adam Brauer <[email protected]>
…nected mode (#808) * Set changeOrigin: true for proxied Sitecore requests in React connected mode - resolves 504 (Gateway Timeout) errors * Add changelog
…new Rest/GraphQLLayoutService implementations do not return HTTP 404 status. Instead, a 200 is returned and a missing route value signifies not found. (#809)
…L + node-headless-SSR-Experience-Edge (#812) * Lint config * Remove serverBundle.defaultLanguage as default language option as it does not exist. * Add 'en' as default fallback langauge
Co-authored-by: Anca Emcken <[email protected]>
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/sitecore-jss/edge-e2e-styleguide/HDci2QMBJCQziYbzXkVPS12B95D8 |
ambrauer
approved these changes
Nov 4, 2021
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.
19.0.0
New Features & Improvements
[sitecore-jss-react][sitecore-jss-nextjs]AddwithDatasourceCheckhigher order component (HOC) to better handle renderings with missing datasources (#723)[sitecore-jss-*]Compile and publish all base package as ESM (#758)[sitecore-jss][sitecore-jss-nextjs][Dictionary Service] [Sitemap Service] Provide ability to customize jssAppTemplateId (#763)[sitecore-jss]Update editing functions for Horizon compatibility (backwards compatible) (#712)[sitecore-jss-nextjs]VERCEL_URLenv variable (if available) for generating public URLs (#725)[sitecore-jss-vue][samples/nextjs][samples/react][samples/angular][samples/vue]dataApi. Replaced byRestLayoutServiceandRestDictionaryService(#744)[samples/react][samples/angular][samples/vue](#773)--fetchWithoption forjss create, which selects REST or GraphQL APIs[samples/nextjs]--emptyflag forjss create(#754)[samples/vue]Upgrade version 2.x to 3.x. Simplify dependencies; remove dependency on i18n (#724)[samples/embedded-app]Remove dependency on StepZilla (#747)[samples/node-headless-ssr-proxy]Remove '/dist' path from pathRewriteExcludeRoutes (#756)Bug Fixes
[sitecore-jss-react][samples/nextjs][samples/react]Fix double rendering (#775)[sitecore-jss-react]Error rendering raw self-closing tag elements in placeholders (#745)[sitecore-jss-react-forms]Experience Forms JSS React implementation doesn't use CSS class applied to entire form (#771)[samples/angular]Fix issue where dk-DA language is not rendered in connected and disconnected mode (#734)[samples/react]Fix 504 (Gateway Timeout) errors for proxied Sitecore requests (visitor identification, media, etc) when running in connected mode (#808)Breaking Changes
[sitecore-jss][sitecore-jss-vue][sitecore-jss-react-native][sitecore-jss-react][sitecore-jss-nextjs][sitecore-jss-angular]Remove deprecateddataApi(#744)[sitecore-jss-*][samples/*]Avoid use of 'any' for TypeScript definitions (#759)