issues Search Results · repo:Lucretiel/kaydle language:Rust
Filter by
11 results
(57 ms)11 results
inLucretiel/kaydle (press backspace or delete to remove)I m trying parse follow txt, but get
called `Result::unwrap()` on an `Err` value: TypeNameMismatch { node_name: server_name , type_name: ServerBlock }
reproduce text
worker_processes 1
events { ...
taikulawo
- 3
- Opened on Aug 9, 2024
- #14
KDL 2.0.0-draft.3 is now generally available (https://github.com/kdl-org/kdl/pull/286), and with it, we ve decided to
encourage existing implementations to start working towards 2.0 support and send feedback ...
enhancement
zkat
- 1
- Opened on Feb 7, 2024
- #13
Implement $kaydle::name magic, for getting the node name in an anonymous node context
magics
Lucretiel
- Opened on Jul 16, 2022
- #10
(Sorry for the meme-y issue title, I couldn t resist)
https://github.com/CAD97/serde-kdl
I m also interested in using KDL in some projects, so I went and wrote some code before I saw that you had some ...
CAD97
- 4
- Opened on Sep 27, 2021
- #9
There are a few cases where we re making a conscious choice to divert from the KDL spec. These should be documented near
the top. Currently this includes:
- Many entities in KDL are defined in terms ...
documentation
- 5
- Opened on Sep 21, 2021
- #8
We should implement the various methods in de::Error to pick out more specific error variants than Custom, where
applicable.
enhancement
- Opened on Sep 14, 2021
- #6
Currently we throw away error locations in pretty much all cases. Variants in the Error enum should retain some useful
context about what went wrong.
enhancement
- Opened on Sep 14, 2021
- #5
Currently we discard all information from parse errors. Use nom-supreme::final-parser utilities to convert nom errors
into a more useful error message. Use ErrorTree for context retention.
- Opened on Sep 14, 2021
- #4
We need to support type annotations. In general we rely on serde to drive the type interpretations, so for 1.0 my intent
is only to parse and discard them. Future support post 1.0 should include:
- ...
bug
- 1
- Opened on Sep 14, 2021
- #3
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Press the /
key to activate the search input again and adjust your query.Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Press the /
key to activate the search input again and adjust your query.