Open GsakuL opened 3 months ago
Nice work! I'll try it when I have some time
I've based
MultiRequest
onGetRequest
. I thought about replacing it, but I'm not sure if that's ok. If there areMigrator
s for Plugin settings, I could add one (forPostRequest
andGetRequest
) , sinceMultiRequest
is supposed to be to handle "all of that and more".
Unfortunately there are no migrators atm, but maybe we can write something manually for the plugin or keep the old actions around for now
I'm still working on it, but it's a bit more than expected at first. I'm creating this draft as some "sort of sign" that work is being done, just a bit slow. I have other stuff going on, so it's not for a lack of trying.
This currently seems to work, but I have not tested every Http-Method and every reply. I also think it's kinda messy, even though I've tried to split this sensibly.
I've based
MultiRequest
onGetRequest
. I thought about replacing it, but I'm not sure if that's ok. If there areMigrator
s for Plugin settings, I could add one (forPostRequest
andGetRequest
) , sinceMultiRequest
is supposed to be to handle "all of that and more".Also unit tests would be nice, but that is itself a big task.
Input from anyone is welcome. However I intend to refactor a bunch to make it easier to read/understand, so smaller comments might be irrelevant later.
but in the end, this would then resolve #2