Why not consume a json schema, like One Table?

[evbo]

Since this repo is opinionated have you ever considered a mode of operation for modyne where it's fed a simple JSON schema file, such as One Table?

Then Rust users can leverage visual design tools that interoperate with One Table, such as Rick Houlihan's Modeler:
https://rh-web-bucket.s3.amazonaws.com/index.html#

Not trying to sound snarky and I respect what you've done here, but modyne comes at a much heavier cognitive load than using the aws sdk directly. One table designs are already pretty high cognitive load as it is, hence why I'm wondering how to lower cognitive load a bit... visualization such as with One Table is an example.

[neoeinstein]

No. Happy for contributions, or derivatives if you have ideas for furthering this. As it stands, Modyne has served our needs wonderfully, shifting complexity to where we thought was best, while making it much less likely that mistakes would be made (especially with added features and maintenance in a table) compared to trying to hold all the invariants in mind while using the SDK directly.

OneTable looks neat, but it was not something that came across as prior art when Modyne was being developed.

JSON may or may not be the best schema format for this. While JSON is idiomatic to TS and JS, there would still need to be code generation for Rust, and writing Rust for Rust was a fine fit. That said, I'm open to contributions that improve the development experience.