Skip to content

Latest commit

 

History

History
58 lines (39 loc) · 1.84 KB

contributions.md

File metadata and controls

58 lines (39 loc) · 1.84 KB

Contributions

We accept contributions. Supply a pull request.

Pre-reqs

Typescript (>=1.6): sudo npm install tsc -g

Install Dev Dependencies from root of repo: npm install

Build

We build the product using npm. Just type npm run build in the root of the repo.

This builds the product in the _build/app directory

C:\tfs-cli>npm run build

Install for Verification

To install the product globally without pushing the npm (you cannot, we do that), run npm install by specifying the directory instead of the name

After building, from the _build directory ...

~/Projects/tfs-cli/_build$ sudo npm install ./app -g
Password:
/usr/local/bin/tfx -> /usr/local/lib/node_modules/tfx-cli/tfx-cli.js
[email protected] /usr/local/lib/node_modules/tfx-cli
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] ([email protected])
└── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])

The product with your local changes is now installed globally. You can now validate your changes as customers would run after installing from npm globally

Tracing

Ensure your changes include ample tracing. After installing your changes globally (above), set TFX_TRACE=1 (export on *nix) and run the tool with your changes. Trace output should validate it's doing what you intended, for the reason you intended and provide tracing for others down the road.

Unit Test

If you're changing core parts of the CL engine, ensure unit tests are run and optionally cover the changes you are making.

TODO: unit testing details (we use mocha) - pending changes