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.
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
(BSR) refactor(typescript): delete some noUncheckedIndexedAccess #7466
base: master
Are you sure you want to change the base?
(BSR) refactor(typescript): delete some noUncheckedIndexedAccess #7466
Changes from 1 commit
91db858
7481345
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
il se passe quoi si
isCurrentQuestionLastQuestion
est falsy et quenextQuestion
est aussi falsy ?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.
rien ne se passe, le type n'autorisait pas de push une nextQuestion à undefined, il y a peut-être du métier à revoir, en cas de doute je peux revert ce code
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.
le type de
PermissionsAndroid.PERMISSIONS
est un record qui a comme valeurs des strings (très permissif) donc on ne peut pas compter dessus pour un fort typage.PermissionsAndroid.requestMultiple
a un typage fort sur le tableau de permissions qui peut lui être passés mais ne fourni pas d'enum de ces strings :(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.
est-ce qu'il serait facile, rapide et pertinent de faire une PR pour améliorer le typage de react-native ?
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.
Il y a une possibilité de créer cet Enum dans notre projet, à voire ensuite pour la maintenabilité.
Avec la méthode ci-dessus, si une autorisation change ou n'existe plus, Typescript ne sera pas content des paramètres qui lui seront passés, même si à priori ça a l'air d'être des plain strings
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.
je proposais de faire une PR sur le projet upstream react-native (pour faire par exemple un enum)