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.
Cette variable d'environnement
BASE_API_URL
(le préfixeVITE
est ajouté par Vite) est définie en production (viadeploy/roles/frontend/templates/frontend.env
). Elle est donc systématiquement présente.Par cohérence, je suis pour n'avoir que l'option
import.meta.env.VITE_BASE_URL
ou bien la supprimer defrontend.env
.(et d'ajouter un commentaire dessus).
Mais du coup, si le code devient :
Alors il serait tout aussi correct d’écrire = ma proposition finale
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 serait aussi + correct d’écrire :
import.meta.env.BASE_URL
quewindow.location.origin
selon moi.