Skip to content

Conversation

@idoraquel
Copy link

@idoraquel idoraquel commented Dec 26, 2019

…on a way from InputInterface::getOption() to ::getFixtures()

Fixes #301

@greg0ire
Copy link
Member

This was introduced in #260 . It looks funny to me that we have to do this… isn't there a way to consistently have an array when calling getOption?

@greg0ire
Copy link
Member

greg0ire commented Dec 30, 2019

Also, looks like the build is broken on at least master and 3.3.x, because of a test that depends on a classname that changed after the last version of the persistence lib was released

@greg0ire greg0ire closed this Jan 24, 2020
@greg0ire greg0ire reopened this Jan 24, 2020
Safe array cast to be sure that we are consistent in interfaces on a way
from InputInterface::getOption() to ::getFixtures().

Fixes #301
@greg0ire greg0ire changed the base branch from master to 3.3.x January 24, 2020 07:02
@greg0ire greg0ire changed the title 301; Safe array cast to be sure that we are consistent in interfaces … Safe array cast to be sure that we are consistent in interfaces … Jan 24, 2020
@greg0ire greg0ire requested a review from weaverryan January 24, 2020 07:03
@alcaeus
Copy link
Member

alcaeus commented Feb 5, 2020

@Codealist why is this necessary? From looking at the code, getOption should always return an array, even if only one option was given. Can you provide a test case that fails with the current code but passes with yours? Thanks!

@alcaeus alcaeus removed the request for review from weaverryan February 5, 2020 08:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants