Wenchy
Maybe need to be discussed deeply, as https://github.com/tableauio/tableau/pull/230#issuecomment-3048158503 points out: > It's too verbose to specify field number for each column. > > Another solution is automation (auto keep compatibilty),...
The specifier need to be discussed in depth. In order to be simple, easy to understand, extensible, and obey consistent design. The general form can be defined as `#VERB(params)`. So...
This PR is not a good idea: - complicated: subtle and tricky - break the rule: what-you-see-is-what-you-get
It's too verbose to specify field number for each column. Another solution is automation (auto keep compatibilty), when compared with the old protoconf file: 1. Auto keep field number by...
Need more common use cases and practices, then we can add common APIs to tableau.
This PR has been superseded by https://github.com/tableauio/tableau/pull/251 .
override: support sheet-level message data overriding for different sheets but same protoconf schema
Maybe using `yaml` is a good format option. And schema checking is guaranteed for `override` option.
Mabye you misunderstand the problem. Problem: For **horizontal two union fields of same union type**, how to resolve it? Solution: Just like https://tableauio.github.io/docs/excel/struct/#custom-named-struct, if custom name explicitly set, then the...
The error module should be set to ModuleConf.
The multikey-map concept is confused. By default, keys are guaranteed to be unique. ## 1. Multi same keys to different values - [C++ std::multimap](https://en.cppreference.com/w/cpp/container/multimap.html) ## 2. A unique composite key...