-
Generator is generating project by default in properties file. Please consider giving option to choose configuration file format.
-
`payu setup` v1.0.19 produces mis-formatted `manifests/input.yaml` in the MOM6-CICE6 iaf config:
https://github.com/COSIMA/MOM6-CICE6/blob/1deg_jra55do_iaf/manifests/input.yaml#L19-L20
-
currently, only JSON format is supported for OpenAPI spec upload.
Please add support for the more common YAML format.
grexe updated
7 months ago
-
As far as I understood the typst team implemented their own [YAML bibliography format](https://github.com/typst/hayagriva/blob/main/docs/file-format.md).
While I am not personally interested in using…
-
### Steps to recreate
* Given any input `dotnet swagger tofile --output docs/swagger.yaml --yaml` where a property has newlines.
For example.
```
///
/// This should look
/// l…
-
## Problem statement
Generated specification is in a wrong yaml format. Notice the `- description: |4-` in specification below. Not sure what might cause that, but it only happens when the `Type` i…
-
### Description of the bug
Hello,
a previous run only providing the unfiltered data worked fine.
I have now added the filtered data from a rerun of scrnaseq just to increase my options.
That addit…
-
## Description
Charmcraft.yaml (replacing metadata.yaml) now removes the need to have different files for metadata, config, and actions. When providing metadata in the charmcraft.yaml format, we ge…
-
The proposed YAML format needs a reader and appropriate integration into the class init function. Probably would be good to have the reader picked based on the file extension (e.g., switching between…
-
My VS Code automatically formats yaml files e.g. to indent lists and add one space before a comment. I'm not sure if we're all using the same one which might be causing some excessive formatting chang…