I think it would be a valuable addition to the alexs-skill-test UI to allow the specification of 'attributes' in the same way we allow for the specification of slots.
Looking at the documentation here, I wouldn't suggest automatically persisting as it says, but handling in the same way we currently handle slots
Reasoning
I'm currently developing a still that uses attributes to help manage internal state and customise the output of my intents. Currently I add attributes manually to the request JSON, but this isn't a very nice UX
Potential solution
With my limited understanding of the code base, I believe we couple duplicate the slot functionality for attributes. This would, however be a fair bit of unnecessary duplication.
Additional
I'm more than happy to work on this if you think it would be valuable and are willing to give me a bit of guidance as to where I should start?
I think it would be a valuable addition to the alexs-skill-test UI to allow the specification of 'attributes' in the same way we allow for the specification of slots.
Looking at the documentation here, I wouldn't suggest automatically persisting as it says, but handling in the same way we currently handle slots
Reasoning
I'm currently developing a still that uses attributes to help manage internal state and customise the output of my intents. Currently I add attributes manually to the request JSON, but this isn't a very nice UX
Potential solution
With my limited understanding of the code base, I believe we couple duplicate the slot functionality for attributes. This would, however be a fair bit of unnecessary duplication.
Additional
I'm more than happy to work on this if you think it would be valuable and are willing to give me a bit of guidance as to where I should start?