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
For example, when the WooCommerce package should be updated (according to WordPress updater page),
one sometimes has to trigger an update on wpackagist.org, otherwise composer update fails.
In order to update the package, one has to first find it on wpackagist.org.
However, the current search finds all kinds of packages that contain the searched keyword woocommerce in their names.
It would be nice if the exact woocommerce package name could be used.
Edit: As a workaround I triggered a package refresh, copied the Fetch-command from Developer Tools, pasted it into Developer Tools console, adjusted the package name and send it manually.
The text was updated successfully, but these errors were encountered:
@strarsis I'm not sure this should be the default, especially as one previous request was basically the opposite: full text index / less exact matching on package titles.
I guess an 'exact' checkbox on the search form would do the job?
For example, when the WooCommerce package should be updated (according to WordPress updater page),
one sometimes has to trigger an update on
wpackagist.org
, otherwisecomposer update
fails.In order to update the package, one has to first find it on
wpackagist.org
.However, the current search finds all kinds of packages that contain the searched keyword
woocommerce
in their names.It would be nice if the exact
woocommerce
package name could be used.Edit: As a workaround I triggered a package refresh, copied the Fetch-command from Developer Tools, pasted it into Developer Tools console, adjusted the package name and send it manually.
The text was updated successfully, but these errors were encountered: