it's too easy to accidentally use host paths in published thunk .jsons

Open vito opened this issue 3 years ago • 1 comments

The v0.1.0 and v0.1.1 releases include .json files that only worked on my machine, because they accidentally embed host paths.

The fix for this is easy case-by-case but this feels like an easy footgun with passing host paths into thunks.

Mar 16 '22 02:03 vito

Being able to encode a host path to JSON is useful for communicating over a local network to an external runtime. (edit: key word being local, since the host paths have to still make sense.)

This might be the cue to introduce a different format for publishing which can be understood by bass -e. The format could dedupe repeated thunks like bass.lock does, and host paths could error when converting to this format.

Mar 19 '22 16:03 vito