add custom js functions for templates
This commit is contained in:
@ -22,8 +22,8 @@ Masonry is a library that provides and implements all the basics necessary to bu
|
||||
|
||||
- [x] Indicate values that are based on Environment variables
|
||||
- [x] On Entities, we should indicate what CRUD functions should be implemented instead of implementing all, or forcing the user to define each in the Endpoints section
|
||||
- [ ] Yaml file to include custom template functions (Otto for JS)
|
||||
- [ ] Support multi-file outputs based on a directory+manifest file.
|
||||
- [x] Yaml file to include custom template functions (Otto for JS)
|
||||
- [x] Support multi-file outputs based on a directory+manifest file.
|
||||
- [ ] Support multi-step generation. e.g. gen the proto file, use `masonry g` to get the basic server set up, gen `main.go` from a template, then update gorm overrides, etc.
|
||||
- [ ] Support field transformations on Entities using a template for `BeforeToORM` in `service.pb.gorm.override.go`
|
||||
|
||||
|
Reference in New Issue
Block a user