@artisan-commerce/builders 0.4.12 → 0.5.0-canary.1

package/CHANGELOG.md

@@ -0,0 +1,105 @@
+# Change Log
+
+All notable changes to this project will be documented in this file.
+See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
+
+## [0.5.0-canary.1](https://bitbucket.org/tradesystem/artisan_monorepo/compare/@artisan-commerce/builders@0.5.0-canary.0...@artisan-commerce/builders@0.5.0-canary.1) (2021-02-12)
+
+**Note:** Version bump only for package @artisan-commerce/builders
+
+
+
+
+
+## [0.5.0-canary.0](https://bitbucket.org/tradesystem/artisan_monorepo/compare/@artisan-commerce/builders@0.4.12-canary.10...@artisan-commerce/builders@0.5.0-canary.0) (2021-02-08)
+
+
+### Features
+
+* **products:** support custome types on modifier groups and normal modifers ([dda6c03](https://bitbucket.org/tradesystem/artisan_monorepo/commit/dda6c03ee8241a5719dcf1745c6a7def83650bda))
+
+
+
+### [0.4.12-canary.10](https://bitbucket.org/tradesystem/artisan_monorepo/compare/@artisan-commerce/builders@0.4.12-canary.9...@artisan-commerce/builders@0.4.12-canary.10) (2021-02-05)
+
+**Note:** Version bump only for package @artisan-commerce/builders
+
+
+
+
+
+### [0.4.12-canary.9](https://bitbucket.org/tradesystem/artisan_monorepo/compare/@artisan-commerce/builders@0.4.12-canary.8...@artisan-commerce/builders@0.4.12-canary.9) (2021-02-05)
+
+**Note:** Version bump only for package @artisan-commerce/builders
+
+
+
+
+
+### [0.4.12-canary.8](https://bitbucket.org/tradesystem/artisan_monorepo/compare/@artisan-commerce/builders@0.4.12-canary.7...@artisan-commerce/builders@0.4.12-canary.8) (2021-02-05)
+
+**Note:** Version bump only for package @artisan-commerce/builders
+
+
+
+
+
+### [0.4.12-canary.7](https://bitbucket.org/tradesystem/artisan_monorepo/compare/@artisan-commerce/builders@0.4.12-canary.6...@artisan-commerce/builders@0.4.12-canary.7) (2021-02-05)
+
+**Note:** Version bump only for package @artisan-commerce/builders
+
+
+
+
+
+### [0.4.12-canary.6](https://bitbucket.org/tradesystem/artisan_monorepo/compare/@artisan-commerce/builders@0.4.12-canary.5...@artisan-commerce/builders@0.4.12-canary.6) (2021-02-04)
+
+**Note:** Version bump only for package @artisan-commerce/builders
+
+
+
+
+
+### [0.4.12-canary.5](https://bitbucket.org/tradesystem/artisan_monorepo/compare/@artisan-commerce/builders@0.4.12-canary.4...@artisan-commerce/builders@0.4.12-canary.5) (2021-02-04)
+
+**Note:** Version bump only for package @artisan-commerce/builders
+
+
+
+
+
+### [0.4.12-canary.4](https://bitbucket.org/tradesystem/artisan_monorepo/compare/@artisan-commerce/builders@0.4.12-canary.3...@artisan-commerce/builders@0.4.12-canary.4) (2021-02-04)
+
+**Note:** Version bump only for package @artisan-commerce/builders
+
+
+
+
+
+### [0.4.12-canary.3](https://bitbucket.org/tradesystem/artisan_monorepo/compare/@artisan-commerce/builders@0.4.12-canary.2...@artisan-commerce/builders@0.4.12-canary.3) (2021-02-04)
+
+**Note:** Version bump only for package @artisan-commerce/builders
+
+
+
+
+
+### [0.4.12-canary.2](https://bitbucket.org/tradesystem/artisan_monorepo/compare/@artisan-commerce/builders@0.4.12-canary.1...@artisan-commerce/builders@0.4.12-canary.2) (2021-02-04)
+
+**Note:** Version bump only for package @artisan-commerce/builders
+
+
+
+
+
+### [0.4.12-canary.1](https://bitbucket.org/tradesystem/artisan_monorepo/compare/@artisan-commerce/builders@0.4.12-canary.0...@artisan-commerce/builders@0.4.12-canary.1) (2021-02-03)
+
+**Note:** Version bump only for package @artisan-commerce/builders
+
+
+
+
+
+## [0.4.12-canary.0](https://bitbucket.org/tradesystem/artisan_monorepo/compare/@artisan-commerce/builders@0.4.11...@artisan-commerce/builders@0.4.12-canary.0) (2021-02-03)
+
+**Note:** Version bump only for package @artisan-commerce/builders

package/README.md

@@ -18,73 +18,73 @@ General representation of the building pieces
 
 In the project directory, you can run:
 
-### `npm start`
+### `yarn start`
 
 Runs the app in the development mode.<br>
 
-### `npm dev`
+### `yarn dev`
 
-Alias of npm start, for some developers convinience.
+Alias of yarn start, for some developers convinience.
 
-### `npm test`
+### `yarn test`
 
 Launches the test runner in the interactive watch mode.<br>
 See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.
 
-### `npm run test:all`
+### `yarn test:all`
 
 Run every test in a none interactive mode and create a coverage report.
 
 This command is perfect for pre push hooks.
 
-### `npm run test:ci`
+### `yarn test:ci`
 
 Simulates a CI environment before running all tests
 
-### `npm run check-types`
+### `yarn check-types`
 
 Will attempt to compile the whole project including test files that are normally excluded.
 
 This command is perfect for verifing the project's integrity before commiting changes
 
-### `npm run lint`
+### `yarn lint`
 
 Runs the configured linter to check for any lints in your code before deploying, developers must clean any lint before commiting or commints will not go through.
 
-### `npm run prettier`
+### `yarn prettier`
 
 Configure prettier, the files that should be included and excluded. This command should not be used by itself.
 
-### `npm run format`
+### `yarn format`
 
 Uses the prettier configuration to run prettier in write mode to all selected files. It will fix all format errors.
 
-### `npm run check-format`
+### `yarn check-format`
 
 Uses the prettier configuration to run prettier in read mode to all selected files. If any is bad formated, it will display a warning.
 
-### `npm run build`
+### `yarn build`
 
 Builds the app for production to the `build` folder.<br>
 It correctly bundles the project in production mode and optimizes the build for the best performance.
 
-### `npm run validate`
+### `yarn validate`
 
 It validates the integrity of the project by running many of the static testing, unit/integration testing and e2e testing commands.
 
-### `npm run validate:ci`
+### `yarn validate:ci`
 
 Run a different series of commands than validate, the selected commands that are run are the ones appropiate to be run on CI. This command is not met to be run locally.
 
 ## Publishing your library
 
-To publish your library you will only need to run `npm publish`. We will take care of the rest. Things like creating a new build of your code will be done automatically. Just take into consideration to bump the project version following the semver methodology.
+To publish your library you will only need to run `yarn publish`. We will take care of the rest. Things like creating a new build of your code will be done automatically. Just take into consideration to bump the project version following the semver methodology.
 
 ## Previewing your library
 
 When you are in the middle of the development of your new library, you find your self needing to test the current features you are developing. We recommend using `npm link` and a separte project for those purposes.
 
-If you want to test your app on a real app, then we recommend using `npm publish`. This method should be avoided during development.
+If you want to test your app on a real app, then we recommend using `yarn publish`. This method should be avoided during development.
 
 > ### Hope you are enjoying this boilerplate
 >