Skip to content

Conversation

@GsakuL
Copy link

@GsakuL GsakuL commented Jul 2, 2024

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 on GetRequest. I thought about replacing it, but I'm not sure if that's ok.
If there are Migrators for Plugin settings, I could add one (for PostRequest and GetRequest) , since MultiRequest 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

@Core447
Copy link
Member

Core447 commented Jul 3, 2024

Nice work! I'll try it when I have some time

@Core447
Copy link
Member

Core447 commented Jul 18, 2024

I've based MultiRequest on GetRequest. I thought about replacing it, but I'm not sure if that's ok.
If there are Migrators for Plugin settings, I could add one (for PostRequest and GetRequest) , since MultiRequest 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

add support for non-json-request/response

2 participants