-
I think it'd be cool to have the list of projects in a machine-readable format somewhere, ideally JSON, I guess. My imagination tells me it'd be really cool to have a browser extension that would use …
-
Even with GHCiD, GHCi responses are simply not machine parseable. There's no reliable grammar and there's no escape support. This is most obvious with the `:show bindings` GHCi builtin command with mu…
-
e.g. JSON with `-j`. This is useful for interacting with graph tools such as mermaid.
-
# Overview
`git machete` is a mega-useful workflow tool,
partially because is nicely separates the current branch state (the git repo state) from a declared target state (the machete config).
I…
-
I used to have a function in my shell that shows when the current directory is running on a multirust toolchain other than stable. The current formatting is making the port to rustup.rs difficult. An …
fenhl updated
4 months ago
-
## Background
Data package licensing is crucial for clearly communicating data usage terms to consumers. Currently, EDI assists data authors by presenting a couple license options aligned with open…
-
### What needs to get done
It would be nice to be able to get the output of `status` as machine-readable formats, such as JSON files
### Why it needs to get done
Useful for parsing store info later…
-
Feature request:
"It would be great if all the column names could be used as R variables
like, ReadsDeam(3term) is quite a challenge"
-
Breaking this out into a new issue for discussion from a couple other spots.
We should establish a format and standard way of accessing machine-readable output, most likely JSON, and then implement…
-
It would be neat if besides human readable description, there is some more formal (maybe executable) description of the code, e.g. as a parity check matrix.
I am setting up some simulation tools fo…