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
Hi. As identified in #83, I think we could use a add_filter sanitize_key to perhaps add more elements to the whitelist. For example, some of our plugins are named something-other.git, to distinguish it from something-other aka clean upstream version. Your thoughts?
The text was updated successfully, but these errors were encountered:
Aah, I see now be16e11 moves away from sanitize_key(), which means we could use a custom filter, or just hardcode to add the . character, since it's likely to be used elsewhere also.
Composer does allow . in package names, so I don't think there should be an issue hardcoding that. If you modify that regex to include ., does it solve your use case?
Hi. As identified in #83, I think we could use a
add_filter sanitize_key
to perhaps add more elements to the whitelist. For example, some of our plugins are namedsomething-other.git
, to distinguish it fromsomething-other
aka clean upstream version. Your thoughts?The text was updated successfully, but these errors were encountered: