-
Add a markdown doc in the repo with our architectural guidelines and decisions.
This will be a living doc that we use to make sure all devs understand the high level direction.
-
At a minimum:
- Add a detection table entry, which following the pattern of other games, will have a puny-encoded unicode filename for the Obsidian Installer. (`Common::punycode_decodefilename` can d…
-
For security purposes, the UDP will need a secure call to this service.
I suspect we'll want the same for the models call, when they implement that.
@cmungall may need to make some architectural dec…
-
-
I just realized that for all our tagging plans, we've not discussed how that front end might look. I've started saving a bunch of links for projects as I work on architectural decisions and it would b…
-
Let's check if we can learn something from these two tools that we can leverage in pylint. I'm thinking either:
- architectural decisions
- interesting checks that might work in Python
- co…
-
As we architecture new changes to the Rune runtime and codegen components we need to understand the tradeoffs.
We need to make some benchmark tests that help keep our eye on the impact of our archite…
-
The root readme should contain general info about how to get up and running. The Readmes in the api (Rails) and future client (React) directories can contain more specific information about the archit…
-
https://github.com/google/pytype/blob/master/docs/errors.md Seems to have a bunch of errors similar to those from pylint. Let's see if we can learn anything from this tool (architectural decisions, ne…
-
As a team member working on this product I want to have one point of reference of agreed architectural decisions and full solution in one place