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
but there are no tool .py files. For now, check_manifest() is okay with this since the exe's are defined, and I kept this the case in my implementation of #1091. However, not having the .py file would eventually lead to an exception in run().
Supposing that these exe's are actually set correctly, do you think we should consider this legal, or should we enforce that there is a .py file for each tool used in the flow?
The text was updated successfully, but these errors were encountered:
A small detail that came up when I was debugging error failures in #1091: do you think we should support configuring tools fully within the schema?
For example, we have a test that sets up some imaginary tools like:
but there are no tool .py files. For now,
check_manifest()
is okay with this since the exe's are defined, and I kept this the case in my implementation of #1091. However, not having the .py file would eventually lead to an exception inrun()
.Supposing that these exe's are actually set correctly, do you think we should consider this legal, or should we enforce that there is a .py file for each tool used in the flow?
The text was updated successfully, but these errors were encountered: