Configuration workaround needed to allow for modular, per-page elements about behatpageobjectextension

[DonCallisto]

@walterdolce I've got this type of organization. I've simply defined my PageNameResolver

<?php

namespace NuvolaBehat\Page;

use SensioLabs\Behat\PageObjectExtension\PageObject\Factory\ClassNameResolver;

class PageNameResolver implements ClassNameResolver
{
    /**
     * @param string $pageFQCN
     *
     * @return string
     */
    public function resolvePage($pageFQCN)
    {
        return $pageFQCN;
    }

    /**
     * @param string $elementFQCN
     *
     * @return string
     */
    public function resolveElement($elementFQCN)
    {
        return $elementFQCN;
    }
}

that work as you expect

$this->homepage->getElement(RegisterButton::class)->click();

[jakzal]

Just FYI, in future versions I'd like to reference page objects by FQCN rather than their name by default.

[DonCallisto]

Cool, when new version comes out, I'll remove my PageNameResolver ;)

[DonCallisto]

@jakzal if you want, I can try to make an implementation for FQCN. Something like: check if it's a valid (existing) one, check if it's an instance of that type (interface) and, then, return it. Maybe I can make a PR with RFC status. Let me know if you agree with this :)

[jakzal]

Sure, PR would be nice :) Could be as simple as returning the class right away if it exists from the existing implementation, or a new implementation.

[jakzal]

I'll close this one as since FQCN is implemented you can put your page objects anywhere.