2.0 Planning #294
Description
As a celebration of Handlebars.Net's millionth installation, it seems like a good time for:
Handlebars.Net Version 2.0 🎉
This thread will be to discuss what goes into 2.0. Really appreciate everyone's involvement, even if it's just bringing your experience and input to the table.
Call for Input
So far, here's the changes being considered (in no particular order): As consensus develops in this thread, approved items will get a [x] to indicate they're officially part of the 2.0 roadmap. Please review, comment, and add your own:
- Make all the function names match handlebars.js (for example, changing
RegisterTemplatetoRegisterPartial) - Be able to return a value from a helper (and generally restructure the helper delegates to be more js-esque) (see Support for returning a complex object from a subexpression #264)
- Support more advanced helper construction (see Question: How to create a custom helper with access to @index #151)
- Add a
Compile<ExpectedModelType>()overload for performance optimization - Support for decorators (see Decorators implementation #137)
- Support the
as |alias|syntax for enumerators (see Sequence contains more than one element #301) - Refactor the compiler so it can provide line numbers of errors and syntax hints (see Add line number in handlebars exceptions #156, Please report betters errors (context) when having mistakes in the template #314)
- Remove the built-in filesystem based templating extension, but ensure we have a good extensibility model so it can still be added as an external plugin
- Support
noEscape(see Can't seem to handle German umlauts.... #276)
Special thanks
to @mcintyre321, @Magentaize, @dejx, @amaclean, @vzwick, @axelheer, @sandorfr, @leniency, @pmccloghrylaing, @mikeprince3, @StefH, @huysentruitw, @abraham-fox, @ondrejtomcik, @mohd-akram, @EBMike, @JvanderStad, @katavasha, @Andrew-Hanlon, @nblumhardt, @crra, @esskar, and the many others who've helped make this library useful to people all over the world in the last 5 years!