Repository navigation
TEST · Fortress — Picker facultatif et réponses Drive par défaut - #31
Draft
iPoower wants to merge 5 commits into
Conversation
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Périmètre isolé
Suite de #30, sans fusion ni publication production. Le chemin Google Drive API
drive.filene dépend plus de la disponibilité de Google Picker au moment de la connexion. Picker reste préchargé en tâche facultative et ne s'ouvre que depuis un clic explicite, une fois prêt.incompleteSearchfacultatif absent = valeur par défaut false (Google Drive v3);true,null, contenu invalide restent rejetés. La validation des dossiers, des propriétaires et de la file est conservée.Tests ajoutés
network.files.listsansincompleteSearch: acceptée ;null: rejetée.Portes
CI à exécuter sur ce SHA ; aucun accès réel ni validation Safari revendiqués. Le transport vendored Race Control devra être synchronisé/attesté séparément avant toute publication TEST intégrée. Aucune modification de
main, secret, scope ou production.