Nick Sutterer
Nick Sutterer
What about making the - somehow clumsy - `has_widgets` block optional in Apotomo? Two simple suggestions. 1. Apotomo could automatically find out which widget is refered to in an event...
This would go into the https://github.com/trailblazer/trailblazer-developer gem: Allow to render terminal-safe activity visualizations using the inflections API. Outcome could be something like this. ``` [Read] -> [your process] -> [Write]...
The circuit doesn't have to be a "dynamic" hash, it can be a stack of compiled methods, optimizing things like linear paths (no `if` needed). This would make TRB incredibly...
```ruby "contract.default"=> "contract" class New < Trailblazer::Cell requires "model", "contract": Reform::Form # typing! end ```
This will utilize the pipe tracking and display helpful stuff in development mode. For example, it could "find out" that `Contract::Validate::Extract` failed because there was no `:key` set.
I see a lot of TRB uses as follows. ```ruby step :check_funds! def check_funds!(options, model:, **) options["contract.default"].errors(:base).add .. end ``` Maybe an injectable, contract-independent result object would be handy, one...
Generate folder structure, operation files, specs/tests, etc. without coupling the generating code to Rails. This can be done with a bit of glue code in `trailblazer-rails`. Related: https://github.com/trailblazer/trailblazer/issues/156
Consider the following "base" operation. ```ruby module MyApp::Operation class New < Trailblazer::Operation step Model( nil, :new ) step Contract::Build( constant: nil ) end end ``` Now, let us use `Nested`...
Given a contract as ``` ruby contract do property :post, populator: { self.post = Post.new } do property :body end end ``` and a different representer in an API-environment mapping...
The internal `@id` given by `VariableMapping()` should be random and unique.