emdoyle / roster Goto Github PK

The repo doesn't have a README.md in the root. Please create one which explains the structure of the project at a high level.

Currently, the PATCH route handler functions match a '{name}' segment which is unused in the handler function body. This is because we use the name in the provided JSON anyway. This means the '{name}' segment is unnecessary, and can be simply removed in all the relevant PATCH routes.

When the app is handling an issue comment, in addition to adding a heart reaction, it should also leave its own comment saying that the feedback has been received.

We use a 'ctags' binary to generate a map of the codebase for Agents to use when generating changes. Our call to 'ctags' includes several flags and options which should be explained in a comment. Please add one!

I want a CLI game in a single Python file which implements the classic rules of Blackjack. The User should be playing against the house, and there should be a nice ASCII display showing the cards on the screen. The House should show one card, and be bound by the typical house rules. The User should be prompted to play another hand after each hand is finished.

Right now, we expose simple HTTP CRUD APIs for several different resources. In the same file where we have implemented this API for Workflows, we should also implement an API for performing operations on WorkflowRecords.

Note that we already have a WorkflowRecordService which should be imported into the api file and used to implement the routes.

Most importantly, we do NOT need to implement any 'write' operations, and therefore only need to expose a GET endpoint (which should accept an ID in the URL) for single records alongside a GET endpoint to list all the records.

The app's settings read environment variables which are all prefixed with "ROSTER_API_".

This is unnecessary since the app is run as a Docker container with its own isolated environment which implies a namespace.

Please stop the settings file from using the prefix.