You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
venvstacks doesn't currently validate that the dependency declarations in each layer are well-formed.
This means that when they're wrong, the user only gets notified via a potentially cryptic locking failure message from uv, rather than being told exactly which dependency declaration is incorrect.
(Since we'll be parsing the input strings anyway, we could even switch to storing the requirements aspackaging.requirement.Requirement instances rather than storing them as plain strings, which would serve to normalize the way they're written out to disk before invoking the locking command. The locking command output is already normalized by the locking tool)
The text was updated successfully, but these errors were encountered:
venvstacks
doesn't currently validate that the dependency declarations in each layer are well-formed.This means that when they're wrong, the user only gets notified via a potentially cryptic locking failure message from
uv
, rather than being told exactly which dependency declaration is incorrect.It shouldn't be difficult to use
packaging
to do a validation pass over the dependency declarations when building the in-memory tree of layer specifications: https://packaging.pypa.io/en/stable/requirements.html(Since we'll be parsing the input strings anyway, we could even switch to storing the requirements as
packaging.requirement.Requirement
instances rather than storing them as plain strings, which would serve to normalize the way they're written out to disk before invoking the locking command. The locking command output is already normalized by the locking tool)The text was updated successfully, but these errors were encountered: