Forms
This library has forms integrated with SalesForce forms. It can be applied to qarson pl website.
Library uses react, typescript, css written in SASS preprocessor.
Developing bundler is webpack.
Build production build made as simple tsc compilation with asset files copies provided
Requirements
Installation:
Installing dependencies
npm install
Build production library files
npm run build
* Build task build two types of library entrypoints :
##Development
Running dev server in standalone mode
npm run start
Running dev mode through bundler in other project.
Project should be linked by npm.
npm run build:dev
* build dev emmits files into dist/esm without CSS / files extraction, it is determined by webpack condition on compilation mode
Running tests
npm run test
####Codestyle
We are in consonance with standardx.
Validation codestyle:
npm run codestyle-check-typescript
Automatic fix:
npm run codestyle-typescript-fix
####CI (bitbucket pipelines)
Checks codestyles and run tests
##Compilation summary
| npm start - (standalone dev) | npm run build:dev (imported as esm in higher bundler) | npm run build (production build) |
---|
key dist files | none | dist/esm/forms-pl.js | dist/esm/forms-pl.js, dist/forms-pl.js, dist/forms-pl.css |
css extraction | no | css in js | esm: css in js, web: extracted |
files extraction | no | yes | no (copied) |
##App configuration | | | |
Forms PL react app requires simple configuration object in window formConfig
property.
Example :
var formConfig = {
locale: 'pl',
formApiSfUrl: 'Salesforce form api url',
formOid: 'salesforce unique environment ID',
}
Object.defineProperty(window, 'formConfig', { value: formConfig })
NPM publising manually:
- Increase version in package.json
- Npm login with proper username and password
npm login
- Npm publish (command will trigger prepare npm method which should build files to dist directory)
npm publish --access=public
NPM publishing through bitbucket pipelines:
-
dev tag publish using pipeline named:
custom: dev-npm-publish
This pipeline automatically defines branch related tag name, for example :
1.0.0-some-branch-name.0
-
production tag publish using pipeline named:
custom: prod-npm-publish
This pipeline requires what kind of semver tag should be defined for publish. You need to fill additional field in pipeline form and type one of version type :
- patch
- minor
- major