Tracking issue for Demo autogeneration backend

[Manishearth]

We'd like to have a backend that lets you autogenerate web demos for the APIs Diplomat exposes.

@ambiguousname is working on this in #500

The list of open issues:

• Demo_Gen: Additional Customization Options #606 (pending resolution with Demo Gen Backend Customization #618)
• Attributes for Param, SelfParam, and StructField types #521
• Demo_Gen: Default Values for Parameters #607
• Demo_Gen: For string parameters, you should be able to set attributes to provide a list of pre-filled options #608
• Demo_Gen: Better Organized Output #609
• Demo_Gen: Improved Error Generation #610
• Demo_Gen: Parameter Naming Conventions #611
• Demo_Gen: Avoid Parameter Name Collisions #612

[ambiguousname]

Copying over my non-blocking issues comment here:

(Potentially) Non-blocking Issues List:

• Because of the new HTML file system, I haven't had a lot of time to add back in things like style or even template customization. Not sure if this is blocking, but I definitely want to add this in before my time with GSoC is up. Demo_Gen: Additional Customization Options #606
• Attribute improvements
  • Attributes for Param, SelfParam, and StructField types #521
  • Default values for parameters (Demo_Gen: Default Values for Parameters #607)
  • Allow selection of pre-set values for strings (Demo_Gen: For string parameters, you should be able to set attributes to provide a list of pre-filled options #608)
• Better organized termini output, instead of a long chain of .apply. Demo_Gen: Better Organized Output #609
• Error generation Demo_Gen: Improved Error Generation #610
  • I think it'd be good to allow generation even if certain errors (maybe just push warnings instead?) are present, so someone could quickly set up a demo and see how it works.
  • Better warnings/error description would be good. Maybe showing the tree of dependencies, so people know where to look.
• Config/Command Line Options Demo_Gen: Additional Customization Options #606
  • Options to set termini to automagically run or be opt-in
• Parameter naming conventions (see WASM Automatic Demo Generator Proof of Concept #500 (comment)) Demo_Gen: Parameter Naming Conventions #611
• Check for parameter name collision (allows us to actually show parameter names in the function definition, and show where each parameter name is going) Demo_Gen: Avoid Parameter Name Collisions #612
• Re-designing ParamInfo, maybe to be clearer whether or not it's an external parameter or one that will be used inside a function. Demo_Gen: Better Organized Output #609
  • See WASM Automatic Demo Generator Proof of Concept #500 (comment)

Issues for each of these to be added after merging #500.

[Manishearth]

Feel free to edit this into a checkbox list in the issue body, fwiw