Skip to content

Export default connect and export default class (FluidNavigator) #22629

Closed

Description

@Sphinx8

Review the documentation: https://facebook.github.io/react-native
Search for existing issues: https://github.com/facebook/react-native/issues
Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment

  "dependencies": {
    "firebase": "^5.0.3",
    "link": "^0.1.5",
    "lodash": "^4.17.11",
    "react": "16.6.1",
    "react-native": "^0.57.5",
    "react-native-fetch-blob": "^0.10.8",
    "react-native-image-picker": "^0.27.1",
    "react-native-router-flux": "^3.40.1",
    "react-navigation": "^3.0.7",
    "react-navigation-fluid-transitions": "^0.2.74",
    "react-redux": "^5.1.1",
    "redux": "^4.0.1",
    "redux-thunk": "^2.3.0"
  },
  "devDependencies": {
    "babel-jest": "23.6.0",
    "jest": "23.6.0",
    "metro-react-native-babel-preset": "0.49.2",
    "react-test-renderer": "16.6.1"
  },

Description

I experience a problem. Export default connect and export default class. How can I use together? Sorry for the basic question

Reproducible Demo

import { connect } from 'react-redux';
import { FluidNavigator } from 'react-navigation-fluid-transitions';
import { kriterDegis, denetimKriter } from '../actions';
...
class Kriter extends Component {
...
render()
...
{this.renderButton()}
...

class Screen2 extends React.Component {
render() 
...
const Navigator = FluidNavigator({
  kriter: {screen: Kriter},
  screen2: {screen: Screen2}
});

export default class Myclass extends Component {
  render() {
    return (
       <Navigator/>
    );
...
const mapToStateProps = ({ kriterResponse }) => {
   const {...
    return { ...
};
export default connect(mapToStateProps, { kriterDegis, denetimKriter })(Kriter);

When I change it as below, I get this error when I click on the button in the Kriter class

export const ConnectedKriter = connect(mapToStateProps, { kriterDegis, denetimKriter })(Kriter);

hata

Activity

  1. added
    Type: QuestionIssues that are actually questions and not bug reports.
    on Dec 13, 2018
  2. react-native-bot commented on Dec 13, 2018

    @react-native-bot
    Collaborator

    We are automatically closing this issue because it does not appear to follow any of the provided issue templates.

    Please make use of the bug report template to let us know about a reproducible bug or regression in the core React Native library.

    If you'd like to propose a change or discuss a feature request, there is a repository dedicated to Discussions and Proposals you may use for this purpose.

  3. locked as resolved and limited conversation to collaborators on Dec 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Ran CommandsOne of our bots successfully processed a command.Resolution: LockedThis issue was locked by the bot.Type: QuestionIssues that are actually questions and not bug reports.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions