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
PR #16 added option to define tools with profiles, but for some production cases it would be helpful to define them per task. That is also possible with the settings, using task path, but it is hard to maintain and there is no visual indication how to know "What tools will be used on this task?".
Suggested implementation
After discussion with @mkolar we've came to possible solution. Attributes were just not designed for this kind of feature. So we still use profiles as base functionality, but we'll also supply option to "override" profiles with "tools" stored to "data".
The text was updated successfully, but these errors were encountered:
Each entity has "data", where we can store custom metadata, e.g. tools overrides. So if task entity has "tools" in "data" it means it completelly skips the profiles logic and uses overrides instead.
Description
PR #16 added option to define tools with profiles, but for some production cases it would be helpful to define them per task. That is also possible with the settings, using task path, but it is hard to maintain and there is no visual indication how to know "What tools will be used on this task?".
Suggested implementation
After discussion with @mkolar we've came to possible solution. Attributes were just not designed for this kind of feature. So we still use profiles as base functionality, but we'll also supply option to "override" profiles with
"tools"
stored to"data"
.The text was updated successfully, but these errors were encountered: