-
Notifications
You must be signed in to change notification settings - Fork 31
refactor: update LDClient to use LDContextPartial for identify methods #1045
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
Open
joker23
wants to merge
2
commits into
main
Choose a base branch
from
skz/sdk-1709/client-sdk-context
base: main
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.
+40
−5
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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 hidden or 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
This file contains hidden or 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
This file contains hidden or 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,25 @@ | ||
| import { | ||
| LDContextCommon, | ||
| LDSingleKindContext as LDSingleKindContextBase, | ||
| } from '@launchdarkly/js-sdk-common'; | ||
|
|
||
| /** | ||
| * A single kind context without a key. When this type of context is used, the key will be generated by the SDK via | ||
| * the {@link ensureKey} function. | ||
| */ | ||
| type singleKindContextWithoutKey = Omit<LDSingleKindContextBase, 'key'>; | ||
|
|
||
| /** | ||
| * A multi kind context without a key. When this type of context is used, the keys will be generated by the SDK via | ||
| * the {@link ensureKey} function. | ||
| */ | ||
| interface multiKindContextWithoutKey { | ||
| kind: 'multi'; | ||
| [kind: string]: 'multi' | LDContextCommon | Omit<LDContextCommon, 'key'>; | ||
| } | ||
|
|
||
| /** | ||
| * A partial context is a context that is missing a key. This is an acceptable form of context to identfy with as | ||
| * the key will be generated by the SDK via the {@link ensureKey} function. | ||
| */ | ||
| export type LDContextPartial = singleKindContextWithoutKey | multiKindContextWithoutKey; |
This file contains hidden or 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
This file contains hidden or 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
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.
I think this typing looks good for a multi-kind context, but not for a single kind context. In that this typing for a single kind would make
keyappear to be not an available option.I wonder if we should just be using basically a copy of the single/multi context kinds with key correct specified as being optional. Then converting that for internal use?
Though, I suppose, it could be an Omit and then & { key?: string }. I want to make sure we have somewhat intelligible code completion though.
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.
Or it could be type
singleKindOptionalKey = Omit<LDSingleKindContextBase, 'key'> | LDSingleKindContextBaseThough again I am not sure how good the intellisense for that would be. Maybe fine.