You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow importing Goatfiles via the use statement from remote locations (inspired by deno's remote imports). This would allow centralizing Goatfiles on internal or external web servers.
Example:
use https://gist.githubusercontent.com/zekroTJA/somegistid/raw/somefileid/login.goat
It should also be possible to fingerprint remote imports with a hash. Example:
use https://gist.githubusercontent.com/zekroTJA/somegistid/raw/somefileid/login.goat@md5:5eb63bbbe01eeed093cb22bb8f5acdc3
This feature also opens some dicussion questions like how should relative imports in remote Goatfiles be handled?
Allow importing Goatfiles via the
use
statement from remote locations (inspired by deno's remote imports). This would allow centralizing Goatfiles on internal or external web servers.Example:
It should also be possible to fingerprint remote imports with a hash. Example:
This feature also opens some dicussion questions like how should relative imports in remote Goatfiles be handled?
Example:
I think, in this case, the
use ./login.goat
should resolve tohttps://gist.githubusercontent.com/zekroTJA/somegistid/raw/somefileid/login.goat
.When a fingerprinted remote Goatfile is specified, imports inside these should be disallowed or must also be fingerprinted.
The text was updated successfully, but these errors were encountered: