Can I work on this issue???

You can mention the below details in this thread:

1. Where are you planning to add this feature in the UI? How will the user know this feature is available ?
2. List of random data you will provide - how will you provide it? what package will you use?
3. We already have environment variables .. will you leverage it?

Implementation Details

• UI Addition:
  This feature will be accessible within the request body editor. Users can invoke it by typing {{ (double curly brackets), which will reveal the list of available random placeholders.

• Random Data Types:
  Initial options will include random values for email, username, names, and potentially others. The faker package in Flutter will be used to generate this data without needing to modify environment variables.

• Package Used:
  I will utilize the faker package for Flutter to generate these random values.

• Environment Variables:
  No need to leverage environment variables for this feature, as the faker package provides sufficient randomness for testing purposes.

As you are a first time contributor to this project, I recommend you to pick up an open issue first and resolve it to get familiar with the codebase, before working on adding this completely new feature.

Alright, Thanks for your response.

First, I’ll identify where user inputs (like email or username) are injected into requests. Then, I’ll create small utility functions to generate random values for common fields (e.g., randomEmail() could combine random strings with @test.com).

Next, I’ll update the request-handling logic to detect placeholders like {{$randomEmail}} in API payloads. Using regex or string replacement, I’ll swap these placeholders with the outputs of the corresponding utility functions just before sending the request.

I’ll ensure this replacement works for all endpoints, nested JSON structures, and repeated fields. To keep it lightweight, I’ll avoid external libraries and stick to simple, APIDash core functionalities,

@ashitaprasad @animator @DenserMeerkat

Please provide me feedback for my approach!

@abhinavs1920 think how you can leverage some concept similar to env variables for this feature.

@abhinavs1920 think how you can leverage some concept similar to env variables for this feature.

I'll use APIDash's current environment variables feature that is very well implemented. I'll add a new section called 'Random Generators' where testers can use special tags like {{$randomEmail}} in their API requests (Or we can use some flag to identify if they are the dummy value placeholders or not). When someone runs the request, the system will automatically replace these tags with fresh random values.

First, I'll update the code to check for these {{$...}} tags after handling normal environment variables. Simple functions will generate the random data. The UI will show examples so testers understand how to use {{$randomUsername}} or {{$randomId}} without confusion(extension of feature). This way I can use the existing implementation.

@abhinavs1920 think how you can leverage some concept similar to env variables for this feature.

I'll use APIDash's current environment variables feature that is very well implemented. I'll add a new section called 'Random Generators' where testers can use special tags like {{$randomEmail}} in their API requests (Or we can use some flag to identify if they are the dummy value placeholders or not). When someone runs the request, the system will automatically replace these tags with fresh random values.

First, I'll update the code to check for these {{$...}} tags after handling normal environment variables. Simple functions will generate the random data. The UI will show examples so testers understand how to use {{$randomUsername}} or {{$randomId}} without confusion(extension of feature). This way I can use the existing implementation.

Random Generators => Fake Data Providers

very nice idea.

@animator
Thanks! Shall I move forward with the implementation I mentioned?

Keeping in mind Fake Data Providers

@abhinavs1920 Yes you can proceed 👍

@animator
I have implemented the Fake Data Providers Pane this way, let me know the changes required.