hof
hof copied to clipboard
hofstadter-io
Framework that joins data models, schemas, code generation, and a task engine. Language and technology agnostic.
do we also expose structural operators into the template system?
The idea here is to have the necessary feature to support a Hugo like content directory, where we have an unbounded depth directory to create files 1-1 for based on...
STR: - go to hof folder - have the latest update already - run the following command `hof update --check`  Expected behavior - should have some type of feedback...
Based on this: https://github.com/hofstadter-io/hof/discussions/148#discussioncomment-5264310 but more in depth and more examples also how to construct? is there anything we can do outside of CUE to "$ref: makepath(value)"? - can we...
So users only have to specify the minimum of entrypoints and not have to set watch files, yet still get the most accurate watch behavior. Might need to infer directories...
something like: ``` package main import ( "os" "reflect" "text/template" ) var fns = template.FuncMap{ "last": func(x int, a interface{}) bool { return x == reflect.ValueOf(a).Len() - 1 }, }...
Currently, we only handle files with a single extension, due to how Go's `filepath.Ext()` works. How can we - [x] handle files with no extension, like `Jenkinsfile` - [x] handle...
Something like: https://github.com/oxsecurity/megalinter maybe just a proxy for it?
This would be helpful on a per-file basis, maybe? How to deal with situations where one file needs to reference another file's path, when that path is generated as part...
Metadata
Owner
Metadata
Framework that joins data models, schemas, code generation, and a task engine. Language and technology agnostic.