alistanis / st Goto Github PK

It would be good to have a function that does not depend on os and flag packages. This way it could be used with gopherjs to implement a webpage with side-by-side text areas.

1. long names for the flags, so they're easier to understand when you're looking at them from a script (e.g. from a go:generate tag).

A more general approach to specifying ignored <types> and <fields> maybe useful.

Like:

<type_list1>:<field_list1>;<type_list2>:<field_list2>;...

Which would be something like:

<type1>,<type2>,...:<field1>,<field2>,...;<type3>,<type4>,...:<field3>,<field4>,...;...

Where <type_list>:<field_list> => ignore these fields in these types

Both <type> and <field> can be * to indicate all.

And allow multiple instances of --ignore so that people with large lists can split it across multiple lines.

Another useful mechanism may be to have the tool use tags that are meant for the tool itself. The tool would read directives for fields from its own tag, remove the tag, and replace it with generated tags.

Add support for go fmt by default.

It might be worthwhile to respect GOFILE set by the golang generator. That way you won't have to hardcode file names in the generator specification.

Comment: In some cases, the help doesn't describe what the default behavior is. For example, it gives ways to set snake case or camel case, but doesn't describe what the default is. Same for -w, it says it changes the behavior to write to the original file, but what's the default?

Write tests like an adult

3.) You have a way to exclude structs, but I really would rather have a way to explicitly include them. Then I could just put a go:generate line above each struct, telling st to generate tags for that one struct, and it would be very clear how those tags are to be maintained right from inside the code.