-
-
Notifications
You must be signed in to change notification settings - Fork 344
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
Make fixturesDir
work again with new filesystem API and fileMatch
#488
Comments
Approved. Also free for all since neither @alp82 nor me have the time to work on this at the moment. Just to add more context, the new default value for [
'**/<fixturesDir>/**/*.{js,jsx,ts,tsx}',
'**/?(*.)fixture?(s).{js,jsx,ts,tsx}'
]
|
We could even go a step further and also introduce a
Or does
|
Good idea. I think keeping them separate is more flexible. So I'm a fan of both |
Both |
What's up?
The new filesystem API allows to change
fileMatch
to search for fixtures at arbitrary locations, which is awesome. But that currently deprecatesfixturesDir
which is sad in my opinion.Mkay, tell me more...
Here is the default definition of
fileMatch
: https://github.com/react-cosmos/react-cosmos/blob/master/packages/react-cosmos-voyager2/src/server/find-fixture-files.js#L20-L21I think this could use a placeholder for or which gets replace when the respective config property is set. That allows people to easily change fixtures folder names without recreating the whole glob schema.
If someone overwrites
fileMatch
,fixturesDir
settings will naturally be ignored.Does that make sense?
The text was updated successfully, but these errors were encountered: