@bloomreach/react-banana-ui 1.42.1 → 1.43.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +0 -2
- package/dist/bloomreach-react-banana-ui.es.js +3666 -3656
- package/dist/bloomreach-react-banana-ui.es.js.map +1 -1
- package/dist/bloomreach-react-banana-ui.umd.js +15 -15
- package/dist/bloomreach-react-banana-ui.umd.js.map +1 -1
- package/dist/src/components/inputs/autocomplete/autocomplete.stories.d.ts +1 -0
- package/dist/src/components/inputs/autocomplete/autocomplete.types.d.ts +24 -0
- package/dist/src/components/inputs/autocomplete-field/autocomplete-field.stories.d.ts +1 -0
- package/package.json +1 -2
package/README.md
CHANGED
|
@@ -172,8 +172,6 @@ This command first runs a quiet Storybook build, then uploads `storybook-static/
|
|
|
172
172
|
We use Docker Compose to manage various services required for local development and testing. The `docker-compose.yml` file defines these services.
|
|
173
173
|
|
|
174
174
|
- **Playwright E2E Testing**: The `e2e` service in `docker-compose.yml` sets up a Playwright test environment within a Docker container, ensuring consistent end-to-end test execution across different environments. You can run these tests using `npm run e2e`.
|
|
175
|
-
- **SonarQube Analysis**: The `sonar` service provides a local SonarQube instance for static code analysis. This helps in identifying code quality and security vulnerabilities early in the development cycle. You can start this service and perform analysis using `npm run sonar` (after configuring SonarQube locally). Ensure the `SONAR_TOKEN` environment variable is set.
|
|
176
|
-
|
|
177
175
|
## Branching types
|
|
178
176
|
|
|
179
177
|
To manage and automate complex release workflow based on multiple Git branches and distribution channels, we utilize the `semantic-release` library. Refer to the [documentation](https://semantic-release.gitbook.io/semantic-release/) for comprehensive details. Our current setup is streamlined but designed for future extensibility.
|