Closed (fixed)
Project:
Bootstrap Layouts
Version:
8.x-5.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
5 Mar 2020 at 09:40 UTC
Updated:
24 Jun 2020 at 19:49 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
pavnish commentedPatch Added
Comment #3
kristen polRemoving outdated tag.
Comment #4
rpayanmI fixed these error reported by
drupal-check:Comment #5
pavnish commentedPatch looks good so i move this to RTBC
Comment #6
mohammed j. razem+1
I have sent the maintainer sdarol100 and markcarver to urge a commit/release.
Comment #7
markhalliwellThere were some issues with the previous patch. I believe I've addressed them.
Please review and test with an actual site/install, then set back to RTBC once you've verified it actually works.
I'll create a new release shortly after.
Comment #8
pavnish commentedComment #9
drupal.ninja03 commentedPatch applied from #7 looks good to me.
Comment #10
markhalliwellCommenting the output a CLI command isn't verification.
Comment #11
drupal.ninja03 commentedHi @markcarver, I see that you have reopened the issue. Can you explain what was the reason?
Comment #12
markhalliwellDid you actually check if both real D8 and D9 installs work?
Comment #13
drupal.ninja03 commentedHi @markcarver, as per the scope of the issue here it was to remove deprecated code that shows up as error when you run upgrade status and drupal-check. And running both the tools show that there are no more deprecation errors so it is good to be deemed compatible with D9 and hence we have the core_version_requirement: ^8 || ^9 to bootstrap_layouts.info.yml to designate that the module is compatible with Drupal 9 hence the issue can be closed as I have tested the patch and it applies correctly.
Comment #14
drupal.ninja03 commentedComment #15
markhalliwellThat isn't what I asked.
Comment #16
drupal.ninja03 commented@markcarver as per the tools that we use: upgrade status and drupal-check, these tools are used mainly to check which code is deprecated and incompatible with D9. The main idea is that if these tools don't throw any error so your code would be compatible with D9. There is no need to manually test it separately as there is no major upgrade changes from D8 to D9 hence these tools should be enough to tell us that.
If in the rare case that we still see issues with the module in D9 then we can create separate issue for that.
Comment #17
divyesh19@markcarver applied patch#7, installed it successfully on d8.8.7 and d9.0.0.
Comment #18
markhalliwellThis is the primary issue I have with tools like this: they're only as good as they were made. Meaning: they only catch very specific rules that they're programmed with. These rules can and often change over time.
In the case of these "deprecations", they are also only as good as "this replaced this". It doesn't mean that it is always the best solution, nor do these tool check for syntax/logical errors that may have been introduced by patches.
That's why I asked for actual testing to ensure that the patch I had originally supplied in #7 was technically working. Thanks @divyesh19 BTW!
I currently don't have any instances of this module spun up. I just made the quick changes based on the previous patch that was submitted (#4) and the few issues I saw with it. I needed legitimate, real-world verification and feedback; not some explanation about how you're using CLI automation tools... I immediately got that from the output you posted; not what I asked for nor needed.
---
That all being said, after working on #3096963: [bootstrap] Drupal 9 support for Bootstrap:
I'm not comfortable with this change. This kind of hard dependency bump should be left to major version bumps, not minor once. Considering that the deprecated code here is pretty much just limited to the messenger service, I'd rather just throw in a simple if statement that can support both.
Comment #19
markhalliwellHere's a much simpler and more appropriate approach to this issue than simply requiring newer APIs and removing the deprecated implementations.
Comment #20
divyesh19thanks for the insights @markcarver, makes sense.
applied #19 cleanly, and installed it on both D8 and D9. works fine!
Comment #21
markhalliwellThanks, @divyesh19!
This is also technically a feature request.
Comment #23
markhalliwellComment #24
markhalliwell