-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Environment #62
Merged
Merged
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
- added composer dependencies `contributte/forms-multiplier` and `spatie/color` - added yarn dependency `vanilla-picker` - added custom AlpineJs color picker component - added environments into the Global Settings - added command `GlobalSettings/PutEnvironmentsCommand` - added event `GlobalSettings/EnvironmentsChanged` - added database migrations - updated mapping for entity `GlobalSettings` - added form validator `UniqueMultiplierValuesValidator` - added options `imports` and `template_variables` for `FormFactoryInterface` - added component `EnvironmentsFormControl` - added evaluation of text color (black or white) according to background color for elements that have configurable color (project color, environment color)
- added database migration - added domain event `ProjectEnvironmentsChanged` - added parameters `environments` to the commands `CreateProjectCommand` and `UpdateProjectCommand` - added checkbox list `Environments` to the Project edit form - replaced text field `color` with new color-picker in the Project edit form
- added database migration - added environment parameter to the domain dommand `StoreConsentCommand` - added optional body parameter `environment` in the Consent API - added filterable column `Environment` in the list of consents - added `environment` int the consent history modal
- added database migration - added domain event `CookieEnvironmentsChanged` - added parameter `environment` in domain commands - added field `environment` in cookie imports and exports - added fields `All environments` and `Environments` in the Cookie edit form - added optional query parameter `environment` in the Cookie API
- added environments to the Dashboard - added column and filter `environments` in the list of cookies - fixed filtering on `projects` in the list of cookies - improved color-picker UI
…ronmentsChanged`, `Project\ProjectEnvironmentsChanged` and `GlobalSettings\EnvironmentsChanged`
- added environments support into cookie table scripts
…Project edit form
- changed environment badges - changed style of environment dropdowns - environments are not visible on the dashboard, the consent list and the integration page if the project has just the default environment
- fixed UI issues - environment dropdowns, colored dots before environment names etc. - added option "all environments" in the dropdown on the Integration page - added dropdown with environments for opening the template in the TemplatesForm (integration) - the Cookies API now supports returning all cookies across environments using the `environment=*` parameter
- the default environment is not `null` anymore but the environment code is `"default"` - a color and name of the default environment is now configurable in the Global settings - modified mogrations associated with environments - environments are not nullable anymore, the code `"default"` is used instead - changed processing of query parameter `environment` in the Cookies API. If to parameter is not defined or it's value is empty then all cookies are returned. - small UI changes
- status code 400 with related message is returned from `/api/crawler/receive-result` endpoint if the project not foud - changed some icons - panels with cookie suggestion types are collapsed by default - changed translation of "private provider" to "project provider"
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.
No description provided.