> Is there some way that we could at least confine field names used for anchors > to some kind of namespace?
Thanks for the prompt review. Another option would be to implement a pydantic root_validator that simply filters out entries at the root level based on a prefix - see here (https://git.launchpad.net/~artivis/lpcraft/tree/lpcraft/config.py?h=feature/yaml-alias-filter#n269). Note that the prefix I used is a simple dot but it could be more elaborated. For instance Docker Compose as a similar mechanism called extension fields using the prefix 'x-' (https://docs.docker.com/compose/compose-file/compose-file-v3/#extension-fields). -- https://code.launchpad.net/~artivis/lpcraft/+git/lpcraft/+merge/435370 Your team Launchpad code reviewers is requested to review the proposed merge of ~artivis/lpcraft:feature/yaml-alias into lpcraft:main. _______________________________________________ Mailing list: https://launchpad.net/~launchpad-reviewers Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-reviewers More help : https://help.launchpad.net/ListHelp
