Overview
Artifact ID: | afa4e7452c759ac21733be2ef9e43700600b304b6808a5fb74810fde644e8897 |
---|---|
Ticket: | 4f25e933fc37b3284ec8c068a1366f70753e7169
yaml / json2huddle |
User & Date: | anonymous 2024-03-25 22:38:58 |
Changes
- assignee changed to: "nobody"
- closer changed to: "nobody"
- comment changed to:
I was using both `yaml` and `json2huddle` at the same time, and the JSON input had a `null` value. the error can be more simply reproduced by e.g. ``` chorler@localhost:~> tclsh % package require yaml 0.4.1 % package require huddle::json 0.1 % package require huddle 0.4 % ::huddle null Invalid subcommand 'null' for type '::huddle::Type_null' ``` IMO - no expert on this: I think this is because `yaml` and `huddle` clash in the `ensemble` null command. Also, `yaml` appears to map this to a `string` when huddle expects `null` as it's own type. I tested a small patch (attached) - it seems to pass existing tests, and tweaking the input to any of the test files to mirror the pkgIndex.tcl does seem to show this failure without.
- foundin changed to: "1.21"
- is_private changed to: "0"
- login: "anonymous"
- mimetype: "text/x-markdown"
- priority changed to: "5 Medium"
- private_contact changed to: "10846ba7bbcbef32a5cbf144d0ddd000cbd507fc"
- resolution changed to: "None"
- severity changed to: "Minor"
- status changed to: "Open"
- submitter changed to: "anonymous"
- subsystem changed to: "yaml"
- title changed to: "yaml / json2huddle"
- type changed to: "Bug"