The n stands for knowledge
Old hacky code is in the old-hacky branch. New hacky code is on master.
This is a shell of a ratpack service. Compared to before this has nice routing and config handling, and some nice jdbc-bits.
Still needs all the old functionality bringing in, perhaps with some thought where things should go. If "doing it right" we should probably have a little more testing on the go than we did.
- Basic server backend
- Add vue front end
- Sort out where the YAML goes
- Parse all the YAML again
- Get runnable answers again
- First answer acceptance test
- Answers with different result shapes
- Answers with query parameters
- of different types
- and different optionality
- Work out if answers are really distinct from queries
- Can we avoid having the entire ResultSet in memory?
- Can we avoid having the entire response text in memory?
- Provide a slightly more standards compliant csv
- Work out how to completely evict all traces of Guice
- Add working vue front end
- Bring back the selenium tests?
- ...have some tests
- Probably some of the config, e.g. datasources should live outside yaml?
- What was reading from a security.properties should probably be a security.yaml
- Observability
- What answers are in use?
- By whom?
- When?
- With what parameters?
- Dashboards
- Query Building
- Error Handling
- All the other things a metabase replacement would need to be useful
- Fine grained permissions
- LDAP?
- Shiny charts & Dashboards
- ...