This project is read-only.

What features would you like to see added?

Oct 14, 2009 at 2:04 PM

Please post here if you've got any suggestions for features you think would be good to have in Flit.

Some ideas of my own include:

  • The ability to create methods that return the current state's instance, rather than transition to a new instance (even if it is the same class)
  • Diagrammatic support for entry point nodes (just to make it obvious where you start)
  • Better error messages for when your DSL can't be parsed
Jun 4, 2010 at 8:27 AM

The ability to create methods that return the current state's instance would be definitely something extremely valuable. For instance in your DatabaseScripter example, the following definition

	Column -> Column[label="Delete"]

add a "name" parameter to the Delete method on the column which is unnecessary. Once you've got hold to a Column instance, you simply want to call Delete() on it.


So is there any plans to include this capability in Flit? Or can you give guidance on how to achieve such functionality?


Best regards

Jun 4, 2010 at 10:50 AM

The column class is partial, you could simply add the method outside of Flit's jurisdiction?

Otherwise it's down to how you write your template, this can pick up custom attributes from the [key=value] section of the dot file. So you could have: 

Column -> Column[label="Delete",selfreferential=true]

And pick that up in your T4?