The module is fully compatible with Drupal 9 on the dev branch, I suggest indicating it already in the info module.
There is a patch. It will remove the warning when using the Acquia upgrade_status module.

CommentFileSizeAuthor
#3 route_condition-drupal9_readiness-3092375-2.patch322 bytesphjou
#2 route_condition.info.yml145 bytesphjou

Comments

phjou created an issue. See original summary.

phjou’s picture

phjou
he/him
Location Vancouver 🇨🇦 🇪🇺
commented
StatusFileSize
new route_condition.info.yml145 bytes
phjou’s picture

phjou
he/him
Location Vancouver 🇨🇦 🇪🇺
commented
StatusFileSize
new route_condition-drupal9_readiness-3092375-2.patch322 bytes

Missclick on the wrong file, sorry.

phjou’s picture

phjou
he/him
Location Vancouver 🇨🇦 🇪🇺
commented
Issue summary: View changes

svendecabooter’s picture

svendecabooter
he/him
Primary language Dutch
Location Gent
commented
Status: Active » Fixed

Thank you for your patch. Committed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented
Issue tags: +Drupal 9 compatibility

Per a Slack discussion with Gábor Hojtsy regarding usage of D9 tags (Drupal 9, Drupal 9 compatibility, Drupal 9 readiness, etc.), "Drupal 9 compatibility" should be used for contributed projects that need updating and "Drupal 9" was the old tag for D8 issues before the D9 branch was ready. Doing tag cleanup here based on that discussion.