-
Notifications
You must be signed in to change notification settings - Fork 15
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
feat(useDataEngine): make engine instance a referential constant #934
Open
Mohammer5
wants to merge
1
commit into
master
Choose a base branch
from
Wrap_engine_in_const_in_custom_provider
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
import { renderHook } from '@testing-library/react-hooks' | ||
import * as React from 'react' | ||
import { CustomDataProvider } from '../components/CustomDataProvider' | ||
import { useDataEngine } from './useDataEngine' | ||
|
||
describe('useDataEngine', () => { | ||
it('should preserve the referential identity of the engine', () => { | ||
const wrapper = ({ children }) => ( | ||
<CustomDataProvider data={{}}>{children}</CustomDataProvider> | ||
) | ||
|
||
const { result, rerender } = renderHook(useDataEngine, { wrapper }) | ||
const { current: firstEngineResult } = result | ||
|
||
rerender() | ||
const { current: secondEngineResult } = result | ||
|
||
expect(firstEngineResult).toBe(secondEngineResult) | ||
}) | ||
}) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,14 @@ | ||
import { useContext } from 'react' | ||
import { useContext, useState } from 'react' | ||
import { DataEngine } from '../../engine' | ||
import { DataContext } from '../context/DataContext' | ||
|
||
export const useDataEngine = () => { | ||
const context = useContext(DataContext) | ||
function useConst<T>(initializer: () => T): T { | ||
const [value] = useState(initializer) | ||
return value | ||
} | ||
|
||
return context.engine | ||
export const useDataEngine = (): DataEngine => { | ||
const context = useContext(DataContext) | ||
const engine = useConst<DataEngine>(() => context.engine) | ||
return engine | ||
} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe something like this instead, to support updates when deps change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note however that this will cause double-renders on dependency updates...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
useInstanceVariable
would be used inDataProvider
andCustomDataProvider
instead of inuseDataEngine
right?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds a lot like we could just use
useMemo
instead ofuseConst
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Mohammer5 this is super old... but no, there's a difference because
useConst
guarantees referential integrity whileuseMemo
might re-initialize in certain situations since it is only considered a performance optimization.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I also figured out the other day that
useMemo
does not guarantee that..I think for simplicity's sake, the following might be the most pragmatic with the least amount of abstractions: