Description
For the Expert to be able to offer things like Editing a node or displaying the debug sidebar with relevant messages, it needs to have some additional awareness of the state of the Node-RED instance. This includes things like:
- Is edit dialog already open or is shade present (meaning we should not offer to Edit a node)
- Is the debug sidebar already open or closed? (i.e dont instruct user to open it if already open!)
- What deploy mode is currently set?
- Is the search already open, and if so, what is the current search query?
- Is the Import dialog open, and if so, what is the current content?
- Is the Export dialog open, and if so, what is the current scope of export?
Some of this state can be obtained via existing Node-RED events, others cannot. We will need to assess the current possibilities and determine if we can either implement the necessary functionality in the assistant or if it requires core changes to Node-RED to add the missing events.
Also note, NR 5 brings many changes to sidebars and shades. We should look at this before NR5 is final.
Epic/Story
No response
Description
For the Expert to be able to offer things like Editing a node or displaying the debug sidebar with relevant messages, it needs to have some additional awareness of the state of the Node-RED instance. This includes things like:
Some of this state can be obtained via existing Node-RED events, others cannot. We will need to assess the current possibilities and determine if we can either implement the necessary functionality in the assistant or if it requires core changes to Node-RED to add the missing events.
Also note, NR 5 brings many changes to sidebars and shades. We should look at this before NR5 is final.
Epic/Story
No response