Hi Dirk. On Wed, Jan 28, 2026 at 5:25 PM Dirk Hohndel via subsurface <[email protected]> wrote: > > I'm clearly missing your point here. > The web UI is a thin flask app that talks to the CLI. The CLI must be built > from the Subsurface source. > > I fail to understand the value of having these extremely tightly couple > components spread over two repos.
I guess the first point is that if we want to treat them as 'extremely tightly coupled components' and not as a pair of implementation and consumer of a well defined API, then the only way to prevent staleness and bitrot is to test end-to-end, i.e. add test automation that spins up a flask web server and tests its output Another point is that I am reasonably certaion that out of the 7 people who are subscribing to alerts in the subsurface application repository, about 5 will see any pull requests for python / html / CSS as annoying noise. And the other two are you and I. > Today the only purpose of the CLI is to be the API that the web UI talks to. I am not sure this is the way I would like to look at it - I think the CLI should be able to stand on its own, and supply data in a way that can be used for other use cases than just the web UI - if this isn't the case then I think we are giving up on an opportunity for others to come up with ways to use it. > And given that approximately seven people look at commits to the repo, I'm > not sure where the problem is. Ironically it had been in the repo for two > weeks and no one even noticed Given that these days almost all of the work in the project is discussed through pull requests, I don't think many (if any) people follow commits in the repo. On Thu, Jan 29, 2026 at 4:59 AM Dirk Hohndel via subsurface <[email protected]> wrote: > Thankfully I implemented this so that you can create a simple git repo > to test against, you don't need the backend service. So there's no upside > to adding XML support to this. Thinking of test automation, having to create a git repository, and then load data into it in some way, before being able to use the CLI to verify that the test data results in expected test outputs is still a reasonable amount of overhead, and brittleness from the loading. If we can point the CLI at an XML file, it will become trivial to repurpose some of the existing test data to verify that it is converted into JSON in the expected way. Ngā mihi Michael Keller _______________________________________________ subsurface mailing list -- [email protected] To unsubscribe send an email to [email protected]
