Skip to content

Conversation

@futtetennista
Copy link

I couldn't find any documentation of flags and I ended up looking at the code. It wasn't clear to me from the current docs:

  1. what was the top-level object name
  2. wether individual flags had to be specified as objects or a list
  • Did you add a new feature to hpack? No
  • Did you add an acceptance test for that new feature to test/EndToEndSpec.hs? Not applicable

I couldn't find any documentation of flags and I ended up looking at the code. It wasn't clear to me from the current docs:

1. what was the top-level object name
2. wether individual flags had to be specified as objects or a list
@ad-si
Copy link

ad-si commented May 3, 2024

@sol Can we please merge this? I was exactly looking for such an example snippet in the readme just now.

Copy link
Collaborator

@mpilgrem mpilgrem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If an example would be helpful to remove that perceived ambiguity, would it not be better to add it to line 151, so that line is something like (given the limitations of tables in Markdown):

| `flags`  | `flag <name>` | | Map from flag name to flag (see [Flags](#flags)) | `flags: { my-cabal-flag: { description: 'Optional description', manual: true, default: false } }` | |

```
flags:
development:
description: A development or production build
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CI is complaining about trailing white space.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants