Bug: Inheritance Issue when more than one child is issue in the same scenario about playwright-bdd HOT 4 OPEN

In homeCardPage, which is the first page, where the app display the cards, for the user to select them.

from playwright-bdd.

This is kind of "expected", but lets discuss the use case.
Looking at the scenario itself, I've marked POM for each step:

  Scenario: Complete todos
    When I add todo "foo" # AdminTodoPage
    And I add todo "bar" # AdminTodoPage
    And I complete todo "bar" # OtherTodoPage
    And I filter todos as "Completed" # TodoPage
    Then visible todos count is 1 # TodoPage

So scenario uses 3 POMs that are in non-linear relationship:

TodoPage
AdminTodoPage extends TodoPage
OtherTodoPage extends TodoPage

Technically we can instantiate two POMs (AdminTodoPage and OtherTodoPage) and call common step (And I filter todos as "Completed") on one of them. But imagine if these POMs have some state created by previous steps? In that case calling common step on one of them can lead to unexpected behavior.

One of the ideas is to introduce config option statelessPoms: true and allow such situations. But I suggest to investigate more do we really need this. Maybe we can solve it with linear inheritance model.
Could you share your real use-case for such inheritance?

from playwright-bdd.

I got an e2e scenario where I need to select some cards, lets call it homeCardsPage (parent). Then I need to check (assert) those cards selected in two different pages: userCardsPage (child1) and emailCardPage(child2). These last two pages share the same list of cards, but they are different pages with different elements, that's why we could say they are siblings. They all share a global variable (fixture) cardList, with the card selected by the user.

When I select cards (homeCardPage)
Then I check cards selected in userPage (userCardPage)
And I send cards selected by email (emailCardPage)

I know that one way to cover this, would be to have two scenarios, one for checking the userCardPage and the other for emailCardPage.
But In the case of an e2e scenario I should be able to assert the same element in different components (pages).
So, making emailCardPage extends userCardPage, to cover the linear inheritance, could be a workaround, but I don't feel its the best solution, because I'm forcing emailCardPage inherit elements that are not needed.

from playwright-bdd.

Fair enough! So in your example, on what fixture should we call the first step I select cards?
I see 3 options:

1. on homeCardPage
2. on userCardPage
3. on emailCardPage

from playwright-bdd.