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
I think that as a workaround it might be ok, but the general policy should be to avoid special symbols completely. Because there is a failure mode, if one package is called hello+, and another is hello-, they will conflict and overwrite each other.
Question to discuss with the team, should we further restrict the Conan 2.0 current validation_pattern = re.compile(r"^[a-z0-9_][a-z0-9_+.-]{1,100}$") validation pattern for the package names?
I think that as a workaround it might be ok, but the general policy should be to avoid special symbols completely. Because there is a failure mode, if one package is called
hello+
, and another ishello-
, they will conflict and overwrite each other.Question to discuss with the team, should we further restrict the Conan 2.0 current
validation_pattern = re.compile(r"^[a-z0-9_][a-z0-9_+.-]{1,100}$")
validation pattern for the package names?Originally posted by @memsharded in #11826 (review)
The text was updated successfully, but these errors were encountered: