sls-dev-tools
sls-dev-tools copied to clipboard
Good First Issue: Store an event history for all previously submitted eventBridge events
Why: When opening the Event Injection modal for a particular eventBus, the tool populates each field (source, detail type, and detail) with the last values used for that eventBus. Allowing all events to be saved, similar to the command history in the terminal, will allow users to quickly test multiple events without having to type the same parameters repeatedly.
Expected Behaviour:
- when using the event injection modal, users can use keypresses to cycle through all events previously injected on that bus
Scope Limit:
- this should at least work for the current session of the tool
- In a future issue/pr, this could be extended to include a persistent event history, by use of a event history file, to allow users to quit the tool and still access previously injected events on reopening the tool
Changes needed:
- When storing events, change the previous event dictionary to map to a list of events instead of a single instance here
- Modify the modal to access the previously submitted event from an array of objects here
- Create a new function to use the list of events to set the text value of all the textboxes using
textboxes[i].setContent(Field)
. It may help to use this for-loop for some inspiration - Trigger this function using a
eventInjectLayout.key()
event