Comments

Kolin created an issue. See original summary.

kolin’s picture

Uploaded the wrong patch. See the patch below

kolin’s picture

StatusFileSize
new639 bytes
kolin’s picture

Status: Needs work » Needs review
borisson_’s picture

Status: Needs review » Needs work
Issue tags: +Novice

I disagree with this, we can also make this constrain to the interface by changing the return FALSE to return [] 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.

nginex’s picture

Issue tags: +LutskGCW19
dhirendra.mishra’s picture

Assigned: kolin » dhirendra.mishra
Issue tags: +ContributionWeekend2019

I will work on this in ContributionWeekend2019

dhirendra.mishra’s picture

Assigned: dhirendra.mishra » Unassigned
Status: Needs work » Needs review
StatusFileSize
new430 bytes

Here is the patch.

joshi.rohit100’s picture

Status: Needs review » Needs work

Patch 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.

ApacheEx’s picture

Status: Needs work » Needs review

I think table will be there as we already doing check for the table in the method earlier

are 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.

alonaoneill’s picture

Status: Needs review » Needs work
Issue tags: +Needs reroll

Needs reroll!
Thanks

valthebald’s picture

Version: 8.6.x-dev » 8.8.x-dev
Status: Needs work » Needs review
Issue tags: -Needs reroll

Patch from #8 cleanly applies to 8.8.x, bumping version

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

james.williams’s picture

Status: Needs review » Closed (outdated)

The AliasStorage class has been rewritten to change path storage entirely. It won't ever return FALSE any more.