-
Notifications
You must be signed in to change notification settings - Fork 299
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
chore(liveness): move liveness example app to its own app (#4451) #4462
Conversation
* chore(liveness): move liveness example app to its own app * address feedback * uppgrade outdated deps * Update examples/next-liveness/.eslintrc Co-authored-by: Caleb Pollman <[email protected]> --------- Co-authored-by: Caleb Pollman <[email protected]>
|
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.
In terms of the code/example app, left some minor questions around configuration/deps but nothing major. Had issues running the React Native app when i checked out and ran locally though, can you sanity check?
"../../environments/*" | ||
] | ||
}, | ||
"incremental": true |
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.
Might have missed this is the prior review but is incremental
now required?
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.
think this may have automatically been added when upgrading next, im not sure if it's needed will check
"react-copy-to-clipboard": "^5.1.0", | ||
"react-dom": "18", | ||
"react-icons": "^4.4.0", | ||
"react-map-gl": "7.0.23", |
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.
Do we need react-map-gl for testing Liveness?
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.
nope good catch, will remove
"@types/node": "^15.12.4", | ||
"@types/react": "^18.2.22", | ||
"eslint": "^8.44.0", | ||
"eslint-config-next": "11.0.1", |
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.
Think the plugin major version might be meant to align with the major version of NextJS
"next-global-css": "^1.1.1", | ||
"react": "17", | ||
"react": "18", | ||
"react-copy-to-clipboard": "^5.1.0", |
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.
Think this is no longer needed?
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 saw some issues with no hoisting react between the two different example apps and figured I may as well upgrade next/react on both example apps.
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.
Meant that clipboard dep since it was just for the Liveness app (i think)
@calebpollman tested on this branch and rn android seemed to work |
Closing this as we are going to maintain liveness v5 on a separate branch |
chore(liveness): move liveness example app to its own app
address feedback
uppgrade outdated deps
Update examples/next-liveness/.eslintrc
Description of changes
Issue #, if available
Description of how you validated changes
Checklist
yarn test
passes and tests are updated/addedsideEffects
field updatedBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.