Check if there's a network request already in flight

[koddsson]

Make sure not to fire off additional requests if there's already one in-flight. I chose to reflect this on the element through the read-only busy attribute.

Fixes #75

[koddsson]

This probably needs a failing test before the fix commit.

[keithamus]

Seems reasonable. Is it instead better to use AbortControllers to close previous requests, so that we always use the latest request?

[koddsson]

Seems reasonable. Is it instead better to use AbortControllers to close previous requests, so that we always use the latest request?

Yeah, I think we could. I wanted to avoid doing multiple requests altogether though since I thought that was an error in itself.

[koddsson]

Seems reasonable. Is it instead better to use AbortControllers to close previous requests, so that we always use the latest request?

Yeah, I think we could. I wanted to avoid doing multiple requests altogether though since I thought that was an error in itself.

I was gonna do this but then we still emit the event twice because #getData still fetches data from the WeakMap and we happily emit the event.

I think we can refactor more in this component to make something like that easier but that would probably result in a breaking change.