Currently, when executing EventGrid functions locally, the extension prompts for an event source and an event type. Each time, the extension opens the remote sample file for the event source/event type combo, and any previous changes or customizations are not preserved after the file is closed. We should make it such that the user can save custom events locally, and reuse them for multiple function executions. However, to do this, we need to remember which function was associated to each file. To implement this, we likely need to implement a virtual file system so we can associate this metadata to each file.
Currently, when executing EventGrid functions locally, the extension prompts for an event source and an event type. Each time, the extension opens the remote sample file for the event source/event type combo, and any previous changes or customizations are not preserved after the file is closed. We should make it such that the user can save custom events locally, and reuse them for multiple function executions. However, to do this, we need to remember which function was associated to each file. To implement this, we likely need to implement a virtual file system so we can associate this metadata to each file.