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
Is your feature request related to a problem? Please describe.
No, see discussion here - #422 (comment)
Describe the solution you'd like
With the move to leveraging external commands for extending the core of slumber, one thing that will be increasingly difficult for users to do is share their configuration with fellow developers. Certainly sharing a file is easy enough, but the chains and requests and future response commands built around that configuration are not captured in that configuration - this makes it difficult for users to share their configuration in a workable state.
We should consider:
adding a field to configuration that allows authors to detail the required external binaries.
at config load, check that dependency array and notify the user if required external binaries are missing.
Describe alternatives you've considered
None - word of mouth communication for dependencies when shared
Additional context
None
The text was updated successfully, but these errors were encountered:
FWIW I think the current alternative is "let it fail", i.e. if someone runs a request with a binary dependency they don't have installed, it should surface an error like my-binary: file not found. I'm not opposed to this feature though. This will have to wait until after The Great Config Refactor though. If the new config language I choose is a general purpose programming language (which is most likely), then what I'm thinking is the ability to run code on startup, as well as a function to check if a particular binary is installed. So an example in a JS-like syntax:
if(!isInstalled("my-binary")){warn("my-binary must be installed");}exportconstprofiles={...};exportconstrequests={...};
Exact design details are dependent on the chosen language, but that's what I'm generally picturing. This will be a few months away at least, but this issue will make sure I don't forget about it. Once the config refactor is done, it should be a pretty easy feature to build.
Did you search for existing issues already?
yup!
Is your feature request related to a problem? Please describe.
No, see discussion here - #422 (comment)
Describe the solution you'd like
With the move to leveraging external commands for extending the core of slumber, one thing that will be increasingly difficult for users to do is share their configuration with fellow developers. Certainly sharing a file is easy enough, but the chains and requests and future response commands built around that configuration are not captured in that configuration - this makes it difficult for users to share their configuration in a workable state.
We should consider:
Describe alternatives you've considered
None - word of mouth communication for dependencies when shared
Additional context
None
The text was updated successfully, but these errors were encountered: