| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Wrote a couple of initial unit tests for some of the logic-heavy points
in the application, being logger.ts and formats.ts. Evidently colorize()
causes an error when transforming on the Format object that's returned.
Since that is specific to the Console transport anyways, I just moved it
to the transport, since the unit test was only testing the passed label
in the returned Formats object.
Also the bash template has some issues that I didn't test (oops), so
those are fixed now.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Unfortunately, a static file can't really be used to serve the
connection - the host address is needed to link back to the server.
Only a light library is needed to handle the template file though,
and if more are needed in the future it should be a non-trivial
task to add them to the process.
By default I'm configuring this to work with drone.io, since that
is the CI that I personally will be using (most likely). It should
be non-trivial to configure other CI to handle the script as well.
|
| | |
|
| |
|
|
|
| |
There is currently no prod start command - this can be adopted later
when desired.
|
| |
|
|
|
|
|
|
|
|
|
| |
This change fixes various issues with the GET endpoints to return more
accurate error messages. It adds business logic error objects that are
returned in a union type in the controllers. This change should help
separate the business logic from the actual errors from upstream
services.
There may be required changes still with handling those upstream errors
via Promises. Integration tests should be added to verify issues.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
With the new process dependency, process handling has been added to
ensure that the ExpressJS server and MongoDB client connections get
closed up properly.
As noted in the Metadata file above the Branch interface, the schema is
definitely not finalized. Eventually metadata will be needed at the repo
level anyways, so reorganizing the document schema is high on the
priority list.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
The generated Tarpaulin HTML report does not have stats to parse via the
DOM - the data is injected via a script tag, which only has line-by-line
coverage, though it includes statistics for each file. The total coverage is
counted by summing the covered/coverable stats reported for each file.
Also, the bad version for express is fixed, and messages are
included for errors that occur for the POST endpoint.
|
| |
|
|
| |
Signed-off-by: Kevin J Hoerr <kjhoerr@protonmail.com>
|
|
|
Initializes project with TypeScript, ExpressJS, and Badgen. Defines
initial (v1) request paths:
GET /bash
GET /v1/:org/:repo/:branch.svg
GET /v1/:org/:repo/:branch.html
GET /v1/:org/:repo/:branch/:commit.svg
GET /v1/:org/:repo/:branch/:commit.html
POST /v1/:org/:repo/:branch/:commit.html?token=&format=
Also sets up interfaces for defining multiple formats. Tarpaulin is
defined but not implemented. All requests (aside from GET /bash)
return 501 NOT IMPLEMENTED.
A global TOKEN is expected for POST request. This can and should be
adapted to assigning tokens per repository, though this may require
verification from the originating repository or administrative
designation.
|
