Changelog
current
- Do correct query for jig-specific progress (bug in implementation in 0.7.1)
- Enable debug logging on the staging environment
- Include Product when getting Samples
0.8.0
- Default GET /testsamples to 100 items per query
- Allow pagination on GET /testsamples
- Allow searching test samples by their product's properties
0.7.1
- Create an invalidated product when updating an existing testsample
- Sort GET /testreports on date
- Allow a jig to get test reports from another jig, as long as the manufacturer is the same
- Allow checking order progress for a specific jig (via query param)
- Add firstPass boolean property to testResult schema
- Fix for subtle looping bug on progress report
0.7.0
- Add email integration for released orders and a generic email message
0.6.4
- Fix issue where wrong product candidate is chosen on POST /testsamples
- Allow bulk creation of test steps
0.6.3
- Allow cascade deletes on the many-to-many relations with Order
- Allow getting MO orders from the Jig
- Infer the manufacturer from the Jig's certificate for test samples (if necessary)
- Fix issue with versions that have an integer-like version such as 1.0
- Only show released orders when query is done by a jig
0.6.2
- Pays back some technical debt
0.6.1
- Publish changelog on root route
0.6.0
- Require authentication for most routes (as defined in spec document)
- Technical: refactor all routes and services into modules for easier imports
0.5.1
- Use the empty name everywhere for hardware and firmware (fixes duplicate custom versions)
- Uniqueness of a sample is on the product type, not the hardware type
- Explicitly ask for a custom producttype's hardwaretype
- Allow querying testsamples on product types (and other criteria)
0.5.0
- Basic email functionality
0.4.2
- Another new unique constraint: scripts must have an unique name + version
- Get the actual error message in the HTTP response
0.4.1
- Support numerical and boolean query params
- Only when testing, allow a longer token expiry time
- Give more information when getting orders / manuf orders
- A custom unique constraint on test-samples: serialNumber + hardwaretype must be unique
0.4.0
- Allow query params on the GET / methods
- Add a GET /options
- Allow finding an order from a Manufacturer Order Number
- Allow only options of different groups on orders
- Allow POST /testsamples to create new (not-validated) products
- Add more unique constraints on the database level
0.3.1
- Don't crash on /progress if an order has no samples
- Clean up versioned-entities APIs
- Make a testSample's serial number required, and a test report's legacyResult optional
0.3.0
- Enable cors
- Sign test jigs with a PEM certificate
- Authenticate a jig by signing its CSR
- Allow authorizing a jig by verifying its JWT token
- Require a JWT token for GET /testsamples
- Add instructions for JWT to README
0.2.1
- Sign samples (devices) with an elliptic key
0.2.0
- Add all CRUD routes for important entities
- Add related entities to GET responses where appropriate
- Big additions to Postman Collections
0.1.1
- REST routes: POST requests for most entities
- Add Swagger docs route
0.1.0
- First datamodel implementation (Prisma)
- REST routes: orders (full API)
- Small Postman Collection added for example requests
0.0.1
- Initial commits, no functionality