Right now, when executing blob trigger functions, whether regular or EventGrid-based, we always prompt the user to enter a path to the blob that the function should trigger on, which is always set to the sample data of samples-workitems/workitem.txt. We should make this experience smoother and more intelligent, by instead listing the blobs in the container that the function is listening for, and allowing the user to pick an actual blob from there, than allow for the potential of the user inputting an invalid path.
P.S., even though this issue affects all blob functions, I am adding the eventgrid tag since this is also relevant to the EventGrid-based blob trigger function, and this idea was brought upon through discussing the local development experience for EventGrid functions.
Right now, when executing blob trigger functions, whether regular or EventGrid-based, we always prompt the user to enter a path to the blob that the function should trigger on, which is always set to the sample data of
samples-workitems/workitem.txt. We should make this experience smoother and more intelligent, by instead listing the blobs in the container that the function is listening for, and allowing the user to pick an actual blob from there, than allow for the potential of the user inputting an invalid path.P.S., even though this issue affects all blob functions, I am adding the
eventgridtag since this is also relevant to the EventGrid-based blob trigger function, and this idea was brought upon through discussing the local development experience for EventGrid functions.