Stripping Input Data from Background Callback Polling

[BSd3v]

Attempting to make polling requests not eat bandwidth

This is to fix #3111

[gvwilson]

@T4rk1n can you please review? thx

[T4rk1n]

Looks good overall. I just have a question if we could just do body = "{}" if we have the cache key instead of setting the inputs to null, think that might require some work on the backend callback but wouldn't it be better?

[BSd3v]

@T4rk1n,

This would indeed take much more effort to unwind how the background callbacks function to completely strip the need for the input structure, as this is used to verify the callback structure, as well as pull things like context (I'm assuming for using things like progress updates)

---

If we want to do this in a rework, it should probably be done with my other open PR, as this will require a much more lengthy refactor. This PR however wouldnt require a rework and would solve the issue with lengthy data being passed to the backend when unnecessary.

[T4rk1n]

This would indeed take much more effort to unwind how the background callbacks function to completely strip the need for the input structure, as this is used to verify the callback structure, as well as pull things like context (I'm assuming for using things like progress updates)

It's fine like this, I don't think the refactor is really worth the effort for now.

[T4rk1n]

💃 Looks good, thank you.

[T4rk1n]

table-node failed with unrelated npm connection error, merging.