Mise en place d'un glossaire et de règles pour doctrine/orm #2114
Conversation
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
stakovicz
reviewed
Jan 15, 2026
Mopolo
force-pushed
the
doc-adr-doctrine-glossaire
branch
from
a379b18 to
f20528c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Suite à la discussion pendant la réunion du pôle outils, voilà un début de glossaire très simple.
J'en ai profité pour rédiger un document qui explicite le choix de la langue et autres pour notre utilisation de
doctrine/orm.Le but ici c'est d'échanger sur tout ça donc n'hésitez pas à remettre des choses en question.