Closed piboistudios closed 2 years ago
Any idea what's going on with the disabled test? Otherwise, I'll try to check it this weekend ;)
Any idea what's going on with the disabled test? Otherwise, I'll try to check it this weekend ;)
Not really. I had to make it dynamic, and also scheme
is actually undefined
(or null
in Haxe) and not ''
as the test case was expecting..
Any idea what's going on with the disabled test? Otherwise, I'll try to check it this weekend ;)
Not really. I had to make it dynamic, and also
scheme
is actuallyundefined
(ornull
in Haxe) and not''
as the test case was expecting..
And yet the test now fails... I am not sure. Probably because I use haxelib PM vs lix PM
kind of like a symlink for APIs? I really like it
or can you just leave the issue123 test unchanged? we can deal with it in another issue if it is still a problem
or can you just leave the issue123 test unchanged? we can deal with it in another issue if it is still a problem
Can you do it in a way such that it shows no changes in this PR?
or can you just leave the issue123 test unchanged? we can deal with it in another issue if it is still a problem
Can you do it in a way such that it shows no changes in this PR?
Yeah, I am not really sure how to do that without opening another PR
Keep committing until the changes disappear in the "Changes" tab in this PR
Yeah, probably instead I just won't make anymore pull requests :). Make it yourself.
It was a simple enough change.
This will allow you to return
tink.web.proxy.Remote
instances from routes like so:Then, using this remote interface as an example:
Response: