| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Especially with the new functionality, the complexity of the command-line
interface alone was really becoming unmanageable. The serdi implementation
also had the highest cyclomatic complexity of the entire codebase by a huge
margin.
So, take a page from the Unix philosophy and split serdi into several more
finely-honed tools that can be freely composed. Though there is still
unfortunately quite a bit of option overlap between them due to the common
details of reading RDF, I think the resulting tools are a lot easier to
understand, both from a user and a developer perspective.
|
|
Though potentially useful, I don't think the complexity cost of the old
interface (both to the implementation and to the user) is worth it. A special
tool to transform blank node labels (for example with regular expressions)
would be a better approach to this if it's ever needed in the future.
|
|
While occasionally useful, I almost always end up reproducing the issue live to
investigate something anyway. Not keeping the many tests results around
results in less clutter, and hopefully makes the test suites faster in
environments with bad I/O like Docker.
|
|
|
|
|
|
This is more powerful, and reduces the number of command line options that
almost nobody needs to care about.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
