As I was staggering back from godawfulkingsheath, I passed a familiar looking young woman.
A few minutes later I realised she looked like Rubathon Blue.
As I was staggering back from godawfulkingsheath, I passed a familiar looking young woman.
A few minutes later I realised she looked like Rubathon Blue.
Aspettando martedì.
🤟🏻Waiting for tuesday🤟🏻
Sorry, in the spirit of "holy fuck" in the strongest sense of the word.
Pretty sure this is the image that proves the thesis... make the right thing to do the obvious thing to do... constrain the solution by providing a substrate that makes the obvious thing to do simple...
And you get a node in your graph that will inject your code from any point in the graph ({{include:${test-ruby-provider:config.function-root}.code}} is valid syntax, ${} then {{}}) and run the provided against it
This is just quick test of the basic case to prove the theory. The full thing involves the full pointer math based include for the code and another for the spec header ({{include:${test-ruby-provider:config.function-root}.test}}) and a test harness to poke('test-ruby-provider:config.function-root', 'my-slug:my-function') and peek('test-ruby-provider')
IE: I can point at any function in the graph, pull in its code and tests, and run them from anywhere, all from markdown.”