Closed (outdated)
Project:
Drupal core
Version:
8.9.x-dev
Component:
path.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
27 Jul 2018 at 10:20 UTC
Updated:
3 Dec 2019 at 12:40 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
kolin commentedUploaded the wrong patch. See the patch below
Comment #3
kolin commentedComment #4
kolin commentedComment #5
borisson_I disagree with this, we can also make this constrain to the interface by changing the
return FALSEtoreturn []in the catch. As far as I can see from the current testcoverage there doesn't seem to be anything that actually tests the return false usecase.So I think we should change to code instead of changing the interface.
Comment #6
nginex commentedComment #7
dhirendra.mishra commentedI will work on this in ContributionWeekend2019
Comment #8
dhirendra.mishra commentedHere is the patch.
Comment #9
joshi.rohit100Patch looks fine to me but I am wondering if this will help as with exception, we call
$this->catchException($e);and this throws exception (although only when table exists and I think table will be there as we already doing check for the table in the method earlier).So not sure if we really need to return something here.
Comment #10
ApacheEx commentedare you sure? it will do check when
$select->execute()is called, so it's done in try / catch. That's why we need to return [] when table doesn't exist and trow exception when table exists.So, patch from #8 looks good for me.
Comment #11
alonaoneill commentedNeeds reroll!
Thanks
Comment #12
valthebaldPatch from #8 cleanly applies to 8.8.x, bumping version
Comment #14
james.williamsThe AliasStorage class has been rewritten to change path storage entirely. It won't ever return FALSE any more.