[Feature Request] Support corn configuration

[fbewivpjsbsby]

Greetings

No response

Feature Request

使用 corn 配置语言，corn 的灵感来自于 json 和 nix，和 dae 相似

Use Cases

目前，我们定义 outbound 时是这样使用的

group {
    example_group {
        # example policy
        policy: example_policy
    }
}

在 corn 中我们可以创建 Key chaining

// example policy
{ group.example_group.policy = "example_policy" }

以及我们可以在 let 中定义后再使用

let {
  $example_policy = "example_policy"
} in {
  group.example_group.policy = $example_policy
}

Potential Benefits

引用 corn 的介绍

Corn has been designed using inspiration from JSON and Nix to produce a language that's easy and intuitive to write, good for config files, and has a feature-set small enough you can learn it in minutes. It was born out of the following frustrations:

• JSON is not a config language, despite how often people use it as one.
• TOML is good for flat structures but gets ugly quickly with deeper objects.
• YAML is far too complex and its whitespace rules make it error-prone.
• Nix is a full-sized language and not easy to integrate.

corn 相比 dae 能够有更多功能，也不像 nix 一般引入过多依赖 相比 dae，corn 更加通用

[dae-prow[bot]]

Thanks for opening this issue!

[mzz2017]

@fbewivpjsbsby corn 本身很好，但我认为太过编程式的语言不太适合没有基础的用户

[piyoki]

@mzz2017 +1

[fbewivpjsbsby]

If you need english version

Feature Request

Use corn configuration language, Corn has been designed using inspiration from JSON and Nix, like dae

Use Cases

Now, We define outbound

group {
    example_group {
        # example policy
        policy: example_policy
    }
}

We can ceate Key chaining in corn

// example policy
{ group.example_group.policy = "example_policy" }

And we can define it in let

let {
  $example_policy = "example_policy"
} in {
  group.example_group.policy = $example_policy
}

Potential Benefits

Corn introduction

Corn has been designed using inspiration from JSON and Nix to produce a language that's easy and intuitive to write, good for config files, and has a feature-set small enough you can learn it in minutes. It was born out of the following frustrations:

• JSON is not a config language, despite how often people use it as one.
• TOML is good for flat structures but gets ugly quickly with deeper objects.
• YAML is far too complex and its whitespace rules make it error-prone.
• Nix is a full-sized language and not easy to integrate.

Corn has more features than dae, and does not add too many dependencies like nix Compared to dae, corn is more universal

[fbewivpjsbsby]

@fbewivpjsbsby corn 本身很好，但我认为太过编程式的语言不太适合没有基础的用户

dae 目前在低嵌套还比较可读取，但比如 dns.routing.request 下就比较容易和 routing 搞错了 以及 node.chains 使用 RoutingA 格式虽然不错，但使用 link 时就会变成

node {
    chains: 'tuic://supersupersupersupersupersupersupersuperlongtuiclink' -> 'vmess://supersupersupersupersupersupersupersuperlongvmesslink' -> 'vmess://supersupersupersupersupersupersupersuperlongvmesslink'
}

更不可读

[mzz2017]

@fbewivpjsbsby 或许两个分别有上手难度和可读性的问题，我们有其他选项吗