Closed (fixed)
Project:
File Entity (fieldable files)
Version:
8.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
23 Mar 2019 at 22:50 UTC
Updated:
13 May 2021 at 18:57 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
sergiu stici commentedHere is the patch, please review.
Comment #4
joseph.olstadHi Sergiu, great work on this, not sure if it'll pass tests though.
For now I parked this in a new branch called 9.x-2.x
Comment #5
berdirWe don't know yet how 9.x versions will look like exactly, but changes are that there will *not* be 9.x branches, deprecations are meant to be committed to 8.x, but there's no urgency to that and shouldn't be done while tests are as broken as they are now.
Comment #6
joseph.olstadI retriggered tests of this patch on the 8.x branch, it might (probably) need(s) a reroll?
Comment #8
joseph.olstadI merged this into the 8.x branch
however it seems there was a fatal error, I will try revert
Comment #9
joseph.olstadmight be testbot issue, but...
Comment #11
joseph.olstadretriggering tests on patch
Comment #12
joseph.olstadnot sure why the patch isn't applying, it applies in my dev
Comment #13
joseph.olstadhead has 3 fails
Comment #14
berdirthe concept of sanitizing tokens has been removed long ago, this option doesn't exist anymore and doesn't need to be considered.
Comment #15
joseph.olstadok so remove the sanitization then? reroll the patch.
Sounds easy enough, any takers?
Comment #16
anmolgoyal74 commentedRo-rolled and removed token sanitizing.
Comment #17
jenlamptonI believe that if you add drupal 9 as an option to the
composer.jsonfile in this project you can get a nice little Compatible with Drupal 9 badge in the Project information section on the module page.Below is a code sample from a module that has the badge.
It also looks like it may possible to get the badge by adding the 'core_version_requirement' key in the modules info.yml file, which, in turn, will add the version to the require section of
composer.json. Example follows.Do you want to include the change in this Patch or open a separate issue?
Comment #18
berdir@jenlampton: That "badge" on the project page is just a text field where the maintainer can add some text, it's not coupled to the module actually being compatible.
That said, yes, this patch should definitely include the .info.yml change.
Comment #19
primsi commentedSome additional work done here. I did most of the WebTestBase > BrowserTestBase migration. This resulted in a bunch of test fails. Resolved most of them, I think 2 are missing.
Another thing that is missing is to fix FileEntityServicesTest. This should either properly extend ResourceTestBase or - per discussion with @berdir - extend BrowserTestBase with some ResourceTestBase addition.
And finally, there are a bunch of deprecation notices reported by test runs.
End note: interdiff might not be 100% accurate, because I apparently had phpstorm option to commit deletions on. Sry for that.
Comment #20
primsi commented... and the interdiff with the patch again.
Comment #21
primsi commentedNope, still not ok.
Comment #22
berdirComment #23
berdirFixed some tests including the REST one and lots of deprecate replacements, should be pretty much done.
Comment #25
berdirSome more fixes/improvements.
Comment #26
berdirAnd the .info.yml change.
Comment #27
berdirCommitted.
Comment #30
luca_loguercio commentedFor anyone looking to apply it to beta 7
Comment #31
sharif.elshobkshy commentedBeta 8 (8.x-2.0-beta8) has fewer D9 requirements.
New patch to address the following D9 requirements in Beta8 version.
Also added some coding standards.
Comment #32
berdirThat file is dead Drupal 7 code, that's going to require a lot more to make sense again. Just ignore it, no need to bother patching that. If anything, create a new issue to figure out if it can safely be removed or if there's anything worth porting over properly.