feat(browsing-context): allow Forest-Context-Url header to give the current browser url of users
#665
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
SteveBunlon
force-pushed
the
feat/add-browser-context-url-header
branch
from
297eda7 to
91db5bc
Compare
SteveBunlon
force-pushed
the
feat/add-browser-context-url-header
branch
from
91db5bc to
2de740a
Compare
… current browser url of users BREAKING CHANGE
SteveBunlon
force-pushed
the
feat/add-browser-context-url-header
branch
from
f392347 to
a55a262
Compare
jeffladiray
approved these changes
Mar 30, 2021
SteveBunlon
changed the title
Forest-Context-Url header to give the current browser url of usersBREAKING CHANGE
SteveBunlon
changed the title
Forest-Context-Url header to give the current browser url of usersBREAKING CHANGEForest-Context-Url header to give the current browser url of users
forest-bot
added a commit
that referenced
this pull request
Mar 30, 2021
# [8.0.0-beta.1](v7.3.1...v8.0.0-beta.1) (2021-03-30) ### Features * **browsing-context:** allow `Forest-Context-Url` header to give the current browser url of users ([#665](#665)) ([a61699a](a61699a)) ### BREAKING CHANGES * **browsing-context:** users willing to use this header needs either to clean the allowed headers or to add this specific header in the CORS configuration
|
🎉 This PR is included in version 8.0.0-beta.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
SteveBunlon
added a commit
that referenced
this pull request
May 26, 2021
… current browser url of users (#665) BREAKING CHANGE: users willing to use this header needs either to clean the allowed headers or to add this specific header in the CORS configuration
SteveBunlon
pushed a commit
that referenced
this pull request
May 26, 2021
# [8.0.0-beta.1](v7.3.1...v8.0.0-beta.1) (2021-03-30) ### Features * **browsing-context:** allow `Forest-Context-Url` header to give the current browser url of users ([#665](#665)) ([a61699a](a61699a)) ### BREAKING CHANGES * **browsing-context:** users willing to use this header needs either to clean the allowed headers or to add this specific header in the CORS configuration
SteveBunlon
added a commit
that referenced
this pull request
May 26, 2021
… current browser url of users (#665) BREAKING CHANGE: users willing to use this header needs either to clean the allowed headers or to add this specific header in the CORS configuration
SteveBunlon
pushed a commit
that referenced
this pull request
May 26, 2021
# [8.0.0-beta.1](v7.3.1...v8.0.0-beta.1) (2021-03-30) ### Features * **browsing-context:** allow `Forest-Context-Url` header to give the current browser url of users ([#665](#665)) ([a61699a](a61699a)) ### BREAKING CHANGES * **browsing-context:** users willing to use this header needs either to clean the allowed headers or to add this specific header in the CORS configuration
forest-bot
added a commit
that referenced
this pull request
May 26, 2021
# [8.0.0-beta.3](v8.0.0-beta.2...v8.0.0-beta.3) (2021-05-26) ### Bug Fixes * **smart-actions-change-hook:** record is no longer altered and is sent correctly ([#728](#728)) ([2ac7af8](2ac7af8)) * distribution charts using groupby on a relationship throws 403 Forbidden ([#725](#725)) ([30e6744](30e6744)) * regression when fetching has-many and not selecting any fields on a hasone/belongsto relation ([#720](#720)) ([74ed623](74ed623)) * **schema:** do not remove primary key fields from the schema when tables have foreign keys that are primary keys ([8844fb5](8844fb5)) * **search:** enable to search for a big integer in an ID field ([#695](#695)) ([9f8132c](9f8132c)) * **search:** searching for a big int value should not break if there is a regular integer field ([#694](#694)) ([af076ad](af076ad)) * **security:** patch ssri dependency vulnerability ([#690](#690)) ([6b0770d](6b0770d)) ### Features * **browsing-context:** allow `Forest-Context-Url` header to give the current browser url of users ([#665](#665)) ([c46fd66](c46fd66)) * **filters:** add support for the \`model.field IN array\` filter condition ([#719](#719)) ([5f58457](5f58457)) * add support for belongsTo and hasOne filters on related data ([#715](#715)) ([2bc769e](2bc769e)) * support yarn 2 plug n play install mode ([#698](#698)) ([64b5734](64b5734)) ### BREAKING CHANGES * **browsing-context:** users willing to use this header needs either to clean the allowed headers or to add this specific header in the CORS configuration
forest-bot
added a commit
that referenced
this pull request
Jul 19, 2021
# [8.0.0](v7.12.2...v8.0.0) (2021-07-19) ### Bug Fixes * abstractRecord type ([#772](#772)) ([81492b9](81492b9)) * correctly get the IP address from the request headers ([2b5ed1d](2b5ed1d)) * fix types ([580ef41](580ef41)) ### Features * allow hooks for global and bulk smart action ([#769](#769)) ([14c26cd](14c26cd)) * **browsing-context:** allow `Forest-Context-Url` header to give the current browser url of users ([#665](#665)) ([c46fd66](c46fd66)) * **browsing-context:** allow `Forest-Context-Url` header to give the current browser url of users ([#665](#665)) ([a61699a](a61699a)) * **security:** secure segments queries ([#764](#764)) ([98d7f74](98d7f74)) * **smart-action:** user can add dynamically field with hook on smart action form ([#742](#742)) ([228bb42](228bb42)) * feat(scopes)!: enforce scopes restrictions on a wider range of requests (#731) ([da7d71d](da7d71d)), closes [#731](#731) ### BREAKING CHANGES * record is no longer send to the hook middleware & values option on smart action is no longer supported * **smart-action:** fields parameters on hook function is no longer a map of field, it is now an array. change hook is no longer choosen by the field name, field need to have hook defined inside it definition by addin a props hook. * the public API of forest-express has changed to include the parameters which are needed to evaluate scope filters. This includes PermissionMiddlewareCreator, all classes on the /exposed folder and most services. Many routes now require providing the current user timezone. * **browsing-context:** users willing to use this header needs either to clean the allowed headers or to add this specific header in the CORS configuration * **browsing-context:** users willing to use this header needs either to clean the allowed headers or to add this specific header in the CORS configuration
|
🎉 This PR is included in version 8.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Pull Request checklist: