-
Notifications
You must be signed in to change notification settings - Fork 13
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
fix(types): improve useDataQuery types #1347
Open
Birkbjo
wants to merge
21
commits into
master
Choose a base branch
from
improved-types
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
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 19 commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
3901cbb
fix: added generic T = QueryResult
eirikhaugstulen afcfdbb
fix: changed to correct import
eirikhaugstulen 8083a27
fix: prettier
eirikhaugstulen 96f7b70
fix: changed name of T
eirikhaugstulen fbcbaa9
fix: prettier
eirikhaugstulen f9594d9
fix(types): improve types for useDataQuery.ts
Birkbjo aebb497
fix: remove unnecessary generic for QueryResultData
Birkbjo de2f3ed
style: fix lint errors
Birkbjo da0871c
docs: add ts example for useDataQuery
Birkbjo 5494a1b
style: format prettier
Birkbjo 96bc853
docs: fix typo in docs
Birkbjo be8a420
fix(data): add Pager type
Birkbjo 7ed0780
docs: add docs for paginatedquery
Birkbjo f890981
fix: simplify query type
Birkbjo 392fd84
fix(engine): add improved types to engine
Birkbjo 00c3fb8
fix: use any for QueryResult
Birkbjo d5a2c7d
Merge branch 'master' into improved-types
Birkbjo 3396b63
fix(test): fix failing test
Birkbjo dbd7659
fix: test
Birkbjo 947304c
docs(usedataquery): add typescript example for multiple paged queries
Birkbjo 4f43f9c
style: run prettier
Birkbjo File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
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
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
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
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
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
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,15 @@ | ||
import { QueryResult } from './Query' | ||
|
||
export type Pager = { | ||
page: number | ||
total: number | ||
pageSize: number | ||
pageCount: number | ||
nextPage: string | ||
} | ||
|
||
export type PaginatedData<T> = T & { pager: Pager } | ||
|
||
export type PaginatedQueryResult<TQueryResult extends QueryResult> = { | ||
[K in keyof TQueryResult]: PaginatedData<TQueryResult[K]> | ||
} |
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
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
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
Oops, something went wrong.
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.
We could potentially use
unknown
here instead, but then we are enforcing consumers to type their data. Which could be a breaking change. But becauseJsonMap
-type don't really work anyway (and you had to do the same thing as in screenshot below), I'm all for usingunknown
if we want to enforce typing the result.any
could be "easier" to use, but of course then you lose the types...If we used
unknown
you would have to do something like this (which you have to do now anyway withJsonMap
: