Support arguments in "require" configuration

[novemberborn]

Prompted by #1665 and inspired by Babel's plugin / preset configuration, it'd be neat to do this:

"ava": {
  "require": [
    ["@babel/register", {
      "ignore": ["test/*"]
    }]
  ]
}

If an array is provided we'd require the module, resolve any __esModules / default shenanigans, and invoke .apply() with the remaining values. We should support any number of arguments.

---

IssueHunt Summary

sculpt0r has been rewarded.

Backers (Total: $40.00)

• issuehunt ($40.00)

Submitted pull Requests

• #3184 feat: handle complex options.require config property

---

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

[Jolo510]

Hey @novemberborn, I'd like to take on this task!

[novemberborn]

@Jolo510 awesome, go for it!

[anayaml]

Hey, @novemberborn, I'd like to work on this task

[novemberborn]

@amslv awesome, thanks!

Since this issue was opened, we added support for ava.config.js files. We need to make sure the arguments can be stringified as JSON and then parsed in the worker processes.

We could do the stringifying and the parsing in the main process first, and then use our "deep equal" logic to make sure the values are the same:

ava/lib/assert.js

Line 282 in 6d12abf

const result = concordance.compare(actual, expected, concordanceOptions);

[IssueHuntBot]

@IssueHunt has funded $40.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[stavalfi]

@novemberborn

I don't understand your comment. are you proposing a way to solve this issue? if yes, can you explain in different way?

@amslv awesome, thanks!

Since this issue was opened, we added support for ava.config.js files. We need to make sure the arguments can be stringified as JSON and then parsed in the worker processes.

We could do the stringifying and the parsing in the main process first, and then use our "deep equal" logic to make sure the values are the same:

ava/lib/assert.js

Line 282 in 6d12abf

const result = concordance.compare(actual, expected, concordanceOptions);

---

I did some research and it seems that i must create a temp-js-file that will contain the call to @babel/register with all it's options and add it to the ava.require section.

do you think my idea is ok?

[novemberborn]

@stavalfi I'm not sure what your question is. Could you rephrase it?

[niteshsarode]

@novemberborn Is anyone working on this issue? Can I give it a try?

[novemberborn]

@niteshsarode please do!

[Om-Vg]

@novemberborn I would like to give this a try if no-one's working on it

[novemberborn]

@OMLAKSHMI yes, that'd be great, thanks.

@niteshsarode please do let us know if you are about to submit a pull request 😄

[webobite]

Hi @novemberborn
I would like to give it a try. Will let u know If I am able to solve this issue.

Thanks

[webobite]

@amslv awesome, thanks!

Since this issue was opened, we added support for ava.config.js files. We need to make sure the arguments can be stringified as JSON and then parsed in the worker processes.

We could do the stringifying and the parsing in the main process first, and then use our "deep equal" logic to make sure the values are the same:

ava/lib/assert.js

Line 282 in 6d12abf

const result = concordance.compare(actual, expected, concordanceOptions);

I would like to ask you about this comment. As in this Comment You stated about the main process One need to compare the JSON(arguments) and then use the deepEqual from assert.js (Correct me If I am wrong). As I am new to this repo Can You let me know where exactly the main process code block is there. I tried to trace it from index,js --> worker/main.js --> and then it goes on to chain () call ...
I am new to openSource community.
So Is their any documentation resource (You can point out if available) to understand the specifically workflow of the AVA testing framework which can be used here ?

[novemberborn]

The main process is what loads the configuration. Essentially we can add a validation step before this return:

ava/lib/load-config.js

Line 163 in b71f396

return config;

You wouldn't use assert.js itself. Load Concordance instead and use the compare() function. I don't think you'd need to pass any options.

[yliu481]

Hi, @novemberborn

Can I work on this issue? I would like to give it a try.

Thanks

[novemberborn]

@abhnvgupta thanks for letting us know @abhnvgupta, better luck next time! 😄

[thyrhone]

is it still possible to work on this?

[novemberborn]

@thyrhone all yours.

[sculpt0r]

Hey @novemberborn , I assume this issue is free to take now? Could you tell me if there is anything special here - since there is a lot of people resign from doing this?

[novemberborn]

@sculpt0r yep. No I don't think there's anything special about it.

[sculpt0r]

So @novemberborn - could you assign me to to this ticket?

[novemberborn]

@sculpt0r just start the work, I doubt anybody will jump in before you.

[1shubhankar9]

@novemberborn could you assign me to this ticket

[BT616]

Can i try this task?

[novemberborn]

This will land in #3184.

[utkarsh-shrivastav77]

Hi is this issue still open

[novemberborn]

No, this will land in #3184.