Tarmac-Styled Code Generation Support

[bibi-reden]

Hello!

This PR is meant to add in the feature requested in #23 related to tarmac code style. I've implemented a solution for this. Utilizing your tests, the emits are as followed so far:

Examples

Luau Emit (4 spaces)

return {
    bar = {
        ["baz.png"] = "rbxassetid://2",
    },
    ["foo.png"] = "rbxassetid://1",
}

Typescript Emit (4 spaces)

declare const assets: {
    bar: {
        "baz.png": "rbxassetid://2",
    },
    "foo.png": "rbxassetid://1",
}
export = assets

This also adds an extra configuration that is tarmac, which will be false by default.

Please feel free to request any changes or provide any edits or questions, and thank you for providing this useful tool!

[jackTabsCode]

Hey, thanks for your work! I haven't had time to look through the full implementation yet, but I am a bit concerned about the organization of code here before that.

Ideally, codegen.rs would contain all codegen related code. So main.rs should not really worry about what format the code is in. Ideally the main function would send off the lockfile to codegen, codegen would path it based on the desired code generation style, and receive back the string needed to write the file, which the main function would do.

So perhaps the structure could look somewhat more like:

main
  codegen/
    mod.rs
    flat.rs
    nested/
      mod.rs
      ast.rs
      ...

for example

Another minor thing-I am not a huge fan of naming the configuration (or the style itself) "tarmac" mode. I would much prefer if it the config option was named "style" and perhaps the options could be "flat" or "nested" (tarmac). We could then say in the readme, if you like the tarmac style, go with nested.

I'm also going to end up putting codegen options, since we have three at this point, in it's own section in the configuration. But this probably belongs in a different PR.

[bibi-reden]

Thanks for your feedback! I got a better understanding of what you would intend for your project, and I will be making the requested changes to the best of my ability.

On the tarmac naming, nested is perfectly fine, and providing a style option in the config is more extendable, I agree with you.
I will make those changes momentarily.

[bibi-reden]

To add to the discussion, would you prefer the config to have a style enum akin to this to replace tarmac: bool?

~ config.rs

#[derive(Debug, Deserialize, Serialize, PartialEq)]
#[serde(rename_all = "snake_case")]
pub enum StyleType {
    Flat,
    Nested
}

In the config I would add a style option, and it would end up looking like this in asphalt.toml

style = "nested"

~ state.rs

pub struct State {
    ...
    pub style: StyleType,
    ...
}

[jackTabsCode]

Yeah, that should work. Let's make sure it's optional and Flat is the default.

[bibi-reden]

I've attempted to implement the concept in the previous comment with this commit: 1757304

[jackTabsCode]

Nice. Can we convert .expect calls to .context to better fit in with the rest of the codebase?

[bibi-reden]

Gotcha! It is done.

[jackTabsCode]

Thank you. I'm not going to release quite yet-going to restructure the config file a little bit, then I'll push out 0.5.0