-
Notifications
You must be signed in to change notification settings - Fork 1
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
Start using @lifeomic/react-client #531
Conversation
Pull Request Test Coverage Report for Build 7974737404Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
I believe I updated all for all of the current features in |
@@ -6,8 +6,8 @@ import axios, { | |||
} from 'axios'; | |||
import { useAuth } from './useAuth'; | |||
import { APIClient } from '@lifeomic/one-query'; | |||
import { RestAPIEndpoints } from '../types/rest-types'; |
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.
Can we now delete the types defined in this file?
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.
Yep, +1 -- there are several big type defs defined in this project that should be deleted.
- fhir api types
- rest api types
- auth api types
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 had a bunch of test errors come up when deleting and moving over so I assumed we needed both but will remove.
@@ -104,6 +113,36 @@ export const useConsent = () => { | |||
useConsentDirectives, | |||
useUpdateProjectConsentDirective, | |||
useShouldRenderConsentScreen, | |||
} as { |
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.
Why did we need this cast?
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.
See slack or the failed earlier builds. Happy to fix some other way but that is what was decided there.
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 are not building the FL member app as an SDK is probably the biggest difference.
Route extends keyof Endpoints & string, | ||
Data = Endpoints[Route]['Response'], | ||
>( | ||
route: Route, | ||
payload: RequestPayloadOf<Endpoints, Route>, | ||
options?: RestrictedUseQueryOptions< | ||
Endpoints[Route]['Response'], | ||
unknown, | ||
Data | ||
>, |
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.
Why did we need this explicit type? I think we didn't have it when we used the library on the FL member app.
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.
See slack or the failed earlier builds. Happy to fix some other way but that is what was decided there.
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 are not building the FL member app as an SDK is probably the biggest difference.
To be clear, tests are working but the build is what is requiring these explicit types because of this setting ts config setting |
🎉 This PR is included in version 11.17.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Changes
@lifeomic/react-client
Screenshots