digits-api-tda is the service responsible for handling TDAmeritrade API data to the main API and the UI. Some endpoints are vanilla i.e. they route to TDA with no processing. Others are tightly coupled to a specific component-API React bridge in DigitsUI.
The below stack is minimal because what this API does is bridge TDA responses to the main API where they can be handled
📁 Library | ⚙ Purpose | 📎 Version |
---|---|---|
NodeJS | Base | 16.18.0 |
express | Session Middleware | 4.18.2 |
consumer
is the key which TDA API uses to make authenticated requests.servicePort
is this service's port. If you change it, you will need to change yourconfig.js
in digits-api-maintdaHost
is the TDA API which I have left in case it changes and for project uniformity.
npm i
Scripts provided in package.json
. It's safe to modify or add additional scripts, but here are the defaults:
npm start
- 🔌 Interfacing [ http ]
- All API routing is done through http requests. It's possible sockets play a role one day.
- 🩺 Monitoring [ http ]
- This API intrinsically reports to digits-api-main
- 🧮 Preprocessing [ node ]
- A lot of the data here is not vanilla routing for TDA, but has heavy preprocessing and remapping before serving to the DigitsUI.
- Initialize beautiful README.md
- Describe service API role
- Add husky pre-commit
- Create mesh diagram
- Explain preprocessor philosophy
- Add historical and realtime quote endpoints
- Docker images
- Kubernetes deployment
[<emoji>] [revert: ?]<type>[(scope)?]: <message>
💥 feat(compiler): add 'comments' option
🐛 fix(compiler): fix some bug
📝 docs(compiler): add some docs
🌷 UI(compiler): better styles
🏰 chore(compiler): Made some changes to the scaffolding
🌐 locale(compiler): Made a small contribution to internationalization
Other commit types: refactor, perf, workflow, build, CI, typos, tests, types, wip, release, dep