Skip to content

Conversation

@Antonio-Bennett
Copy link

Hey! Not sure if I'm doing this right but I would love to have access to the helpers module in faker so I've gone ahead and made those changes. I'm using a local plugin right now but thought contributing might be helpful. I also made the module access less of a pain for you I think.

@Antonio-Bennett
Copy link
Author

Trying to figure it out but last thing would be having functions that take arguments like helpers.arrayElement work. So I could for example with my current use case randomize the country/address of orders in a request chain based on the available regions we ship to.

@Antonio-Bennett
Copy link
Author

Antonio-Bennett commented Oct 28, 2025

Hmm a bit stuck in terms of figuring out how to have the argument be reactive to response.body.path

Don't think I need this actually arguments and new modules are good enough I think to do whatever is necessary okay we're good if we have JSON.parse support which I'm not seeing?

Okay ended up just copying the result of previous request and pasting it into the args of faker arrayElement since arguments in yaak can't be variables I can't depend on a response.body.path request chain or other vars

@Antonio-Bennett
Copy link
Author

Can close this PR honestly I don't think until yaak can support variables as args or lazy evaluating them or even actually pre/post scripts this is gonna work like I want. Made a vid just in case I'm missing something

Screenshare.-.2025-10-28.12_28_17.PM.mp4

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.

1 participant