-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Zero documentation for configure()
options
#2533
Comments
Other than A PR making this clearer in the docs would be appreciated. |
You brought up a good point. Is that true, that there is no way to configure enzyme/adapters? I just updated my issue description, the gist being that I wanted to change one of the settings in an adapter that was (dare I say, "clearly?") marked as an entry in |
I’m not sure what you mean by “no way to configure” - the adapter generally decides what configuration options it takes. |
Sorry, "no way to configure" was in response to:
Basically I was just asking for clarification on this. Did you mean there is no way to configure adapter-specific options depending on their usage/internal logic or is there actually a way, it's just not documented? i.e. Only accepting the same |
Of course you can - each adapter can accept any options it wants, and do anything it likes with them. All of the official adapters peel off the adapter-specific options and pass the rest into shallow/mount. |
Current behavior
No resources anywhere show how to configure Enzyme outside of
configure({ adapter: new MyAdapter() })
, including the home page, GitHub ReadMe, test library guides, and adapter guides.There are clearly ways to configure enzyme and adapters, but it's not clear if they should be done via:
configure({ adapter: new MyAdapter({ ...myOptions )) })
configure({ adapter: new MyAdapter(), ...myOptions })
configure({ adapter: new MyAdapter({ ...someOptions }), ...otherOptions })
Expected behavior
Each and every function, especially those with configurable options and even more especially those created by the enzyme team itself, to be documented. We should be able to see pages like
and
and
Example
FWIW, what I wanted to do was to change enzyme-adapter-react-16's
getSnapshotBeforeUpdate
tofalse
so it waits for updates before taking snapshots, globally, for every test (suite).Your environment
API
Version
The text was updated successfully, but these errors were encountered: