-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: support all input fields as query params in standby (mainly proxy) #59
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it makes sense to support all of the input parameters. There is just a small issue with duplicate code which produces duplicate log messages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point about removing query parameters from the README—it will simplify things.
I think we should only provide examples for non-obvious ones, such as outputFormats
. Let’s handle this in another PR. I’ve created an issue for it: #62
I believe Matyáš meant removing the checkAndRemoveExtraParams
function, as it is no longer needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue is fixed, thank you.
At first I did but looking at it closer now I can see that these functions aren't identical. The So I guess this begs a bigger question whether we need the defaults object when we can read the input schema directly. What do you think? |
@matyascimbulka Good catch. Fixed to iterate all @jirispilka I removed the This got quite complex for such a small change (that I need for one customer) so before any further updates, I would do a larger refactor to make future updates easier. I would start with looking at the input, we could officially deprecate some fields (e.g. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that the larger refactor for the input handling and types around it would be useful. But lets not block this PR for that.
Ok, thank you. Yeah, it seems a bit complicated now. |
I tested this locally. I think we could get rid of the Readme section about query params and just send users to https://apify.com/apify/rag-web-browser/input-schema so we don't have duplicate documentation.