-
It would be nice if our output files were self-documenting, with descriptions of what each variable means included in the netCDF files.
I've added the machinery for adding 'description's as attribu…
-
**Epic label**: `E:3.4 Self-documenting Rest APIs`
**Planned start date**: 01/12/2023
**Due date**: 31/12/2023
# Summary
Within the `services` repository, there are two Rest APIs that ar…
mfw78 updated
5 months ago
-
### Configuration
Considerations:
- Needs object and comment support (IMO yaml)
- Make it very obvious what is enabled and disabled (explicit `enabled: true`, not a mix of env vars magically tu…
-
I think each plugin should come with documentation about detection rules, etc. These could then be aggregated and displayed in-app at `help/plugins` or something like that.
As a stop-gap, I created h…
-
Could we do something like:
```rust
offer!(in chan {
End => break chan.close(),
Push => {
// push a value
}
})?;
```
`End` and `Push` would reduce to enums:
```rust…
-
Seems reasonable.
-
Is the next function is really pure? Every time it will produce new function
```
const signUp = (Db, Email, attrs) => () => {
const user = saveUser(Db, attrs);
welcomeUser(Email, user);
};
`…
-
I was chatting today with @tigert and @bproffitt about ci testing to catch things like little gem issues with jekyll-springboard before we hit them during the design process (I've asked @duck-rh to he…
-
In a statement like `@mark.timeout(50)` there is nothing to say the duration is defined in *seconds.* This has a few disadvantages:
- Many other timing mechanisms use milliseconds or minutes as the…
l0b0 updated
9 months ago
-
The zipfile needs to be thoroughly self-documenting.
Include the following:
### The URL that recreates this download
fragalysis-download-link.URL - text file containing the URL that is also r…