Closed jenlampton closed 2 years ago
I've pushed some commits that added Field data:
I've pushed some commits that added paragraph info:
I've pushed an update that adds views data, and ads color coding. Things that need to be changed before an upgrade are red (error) and things that could use a review are yellow (warning).
I've added a "todo" list to the top of this form, but now I'm wondering if having it right there is best, or if it should be provided by a separate submodule?
Originally I was thinking having it here could be helpful, as it would inform people in the "evaluation" phase what to do during the upgrade. But now I'm wondering about that... could use some input!
I've now also added three sections for modules: core, contrib, and custom. Each shows enabled projects, and suggestions about how to handle each one:
Core:
Contrib:
I've added a section for features:
Sounds like a good plan. Go for it.
The report it's a GREAT idea, Jen! Please do it!
Do it!!!
Thumbs up @jenlampton . Didn't see this until now
This looks really great Jen, let's do it!
Thanks everyone! I've merged the PR :)
I have a spreadsheet that I prepare when I'm working on Drupal to Backdrop upgrades, and it includes a tab for contrib modules, but also has a bunch of other information. I'd love to automate the collection and display of this information from existing Drupal 7 sites, and it seems that there's no better place for it than within this module. I haven't yet decided where it should go (perhaps on sub-tabs? Perhaps a separate report page?) but here's a list of what I'd like to include:
I'm not yet sure how to tackle these, since it will involve some "evaluation" of the custom code, but maybe for now we can simply list that these exist, and expand information about them at a later point in time?
And here are some nice-to-haves