Expose the project browser as a render element

yash.rode → made their first commit to this issue’s fork.

@yash.rode
Great work.

Tried the element on a Custom Form

$form['pb'] = [
      '#type' => 'project_browser',
];

and it worked well.

But I see there is another property #source I am assuming this is to restrict the list to the supplied source only like drupal_core or drupalorg_jsonapi source etc. I tried this property but nothing happening. Both sources are already enabled.

Could you please provide some details on how to use these properties #source and #id?

Thanks

Hi @Prashant.c as you can see the path /admin/modules/browse/{source}/{id}' when viewing the /admin/modules/browse page both $source and $id are null and for a details page like http://starshot.test/admin/modules/browse/recipes/drupal-core-core_recommended_admin_theme where source is recipes and id is drupal-core-core_recommended_admin_theme. In that case one can use the #source and #id to see the detail page of specific recipes/module.

Pretty close, just a few more points.

#7 📌 Expose the project browser as a render element Needs work , thanks for the clarifications, as mentioned by @phenaproxima having the properties documented in the the doc comments would be helpful.

@yash.rode pointed me to a very tricky bug, and I found the root cause -- but credit where credit is due, I wouldn't have been able to trace it if @yash.rode hadn't expertly isolated the problem. That's fixed now.

Other than that, I think this MR looks great. Ship it!

Ugh, guess we need a little more work to get the tests passing. Poop.

The test failure is because of 🐛 Remove Modals after They're Closed Fixed which is merged in upstream.

It looks like this test failinghttps://git.drupalcode.org/project/project_browser/-/blob/2.0.x/tests/src/FunctionalJavascript/ProjectBrowserUiTest.php?ref_type=heads

Excellent behind-the-scenes work

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