• Handle Enums
• Think about Blocks
• Better handling of structs

I tried using nom in this branch.

• I tried for hours to figure out the right macros to use to parse the sign of a number...
• It's hard to use. There aren't many good tutorials.
• Macros.... 🤮

Alternatives:

• https://github.com/J-F-Liu/pom
• https://github.com/pest-parser/pest
• https://github.com/kevinmehall/rust-peg
• https://github.com/m4rw3r/chomp
• https://github.com/Marwes/combine
• https://github.com/lalrpop/lalrpop

Reading Materials:

• https://freemasen.github.io/parsers_presentation/

What do you think @gyng?

Hey! Love this crate.

Is there any functionality to parse HCL files into a collection of structs?

I would assume that some_type "some_label" { ... } would deserialize into some struct SomeType { labels: vec!["some_label"], ... }

I can see this project has not been worked on for a while, maybe you could point me in the right direction? (I realise you can already deserialize the body into a struct, but that doesn't really help me out.) I would love to contribute if you could point me in the right direction.

In the future:

• Schema driven deserialization of blocks including whether to assign block labels are enum variants or actual strings in the block body.
• For enums, they will be strictly be treated as "externally tagged" which is Serde's default

For now (and the default behvaiour in the absence of a schema provided):

• Objects will be deserialized as-is to maps/structs (visit_map)
• Blocks will be deserialized to maps/structs via visit_map if the Deserialize implementation does not give any hints. What happens if multiple blocks of the same type exist?
• If hinted to be an enum, all the labels will be concatenated (how?) to form the variant name. Users can customise the matching variant by using Serde's renaming attributes. (consider only the first label?)

What about:

• Internally tagged: Probably cannot use any block labels as aid. If used, will be treated as dumb nested maps/blocks
• Adjacently Tagged: Same as above
• Untagged: Probably same as above

https://github.com/hashicorp/hcl/blob/65a6292f0157eff210d03ed1bf6c59b190b8b906/hcl/token/token.go#L174

serde does not allow such complicated behaviour to be done with Serializers/Deserializers.

Cannot define custom attributes.

Terraform < 0.12 uses a combination of HCL with HIL

Terraform >= 0.12 combines those two together in HCL2

Use https://github.com/fflorent/nom_locate

https://github.com/Geal/nom/blob/master/doc/upgrading_to_nom_5.md