TransitionConfig is a required prop?
See original GitHub issueI started seeing these warnings in my tests recently:
console.error node_modules/fbjs/lib/warning.js:33
Warning: Failed prop type: The prop `transitionConfig` is marked as required in `Loader`, but its value is `undefined`.
in Loader
Is transitionConfig now required on all usages?
I found the change in this diff: https://github.com/nygardk/react-loader-advanced/commit/ec0bd466850e8a2da22548f01928028b9e9e86ed
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Customizable per-screen transitions with StackNavigator #10
Recently I needed to customize screen transition animation for a single screen and it wasn't really straightforward. This proposal aims to ...
Read more >StackNavigator reference - React Navigation
transitionConfig - Function to return an object that is merged with the default screen transitions (take a look at TransitionConfig in type definitions)....
Read more >React Navigation V3 handling transitions and animations ...
and here is the transitionConfig that I had declared. ... isAuth ? this.props.navigation.navigate({ params: { transition: 'transition' } ...
Read more >createStackNavigator - React Navigation - Netlify
Provides a way for your app to transition between screens where each new screen is placed on top of a stack.
Read more >Spring Configs | React Spring
Part of a component's configuration argument, the config prop is an ... Its still part of the easings object but you need to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Sorry, it was made required by accident. Fixed in v. 1.7.1.
Thanks @nygardk!