We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The get method in stateGetter is failing when using a non Immutable store: `
export const get = (state, key, entry) => {
if (!state) { return null; } const isImmutable = typeof state.get === 'function'; const stateItem = isImmutable ? state.get(key) : state[key]; if (!stateItem) { return null; } return stateItem.get(entry);
};
`
Last line should be return isImmutable ? stateItem.get(entry) : stateItem[entry];
return isImmutable ? stateItem.get(entry) : stateItem[entry];
Trying to put together a Pull Request, but having some issues with the build for some reason.
Associated test in stateGetter.test.js `
it('Should return state when its not stored using immutable', () => { const state = { data: { thing: [1] } }; const props = {};
expect( stateGetter(state, props, 'data', 'thing') ).toEqual(List([1])); });
});
The text was updated successfully, but these errors were encountered:
A pull request would be great, what build issues are you having?
Sorry, something went wrong.
Needed to upgrade node apparently. Working on getting a PR working.
This issue was resolved with #179
No branches or pull requests
The get method in stateGetter is failing when using a non Immutable store:
`
export const get = (state, key, entry) => {
};
`
Last line should be
return isImmutable ? stateItem.get(entry) : stateItem[entry];
Trying to put together a Pull Request, but having some issues with the build for some reason.
Associated test in stateGetter.test.js
`
it('Should return state when its not stored using immutable', () => {
const state = { data: { thing: [1] } };
const props = {};
});
`
The text was updated successfully, but these errors were encountered: