JUnit Local/Remote wording for OperatorExtension is not meaningfull to me #1215

Activity

1. csviri commented on May 16, 2022

   

   csviri

   on May 16, 2022

   Collaborator

   More actions

   recently this was renamed to LocalOperatorExtension and ClusterOperatorExtension. Does this sound better also for you?
2. metacosm commented on May 16, 2022

   

   metacosm

   on May 16, 2022

   Collaborator

   More actions

   Maybe LocallyRunOperatorExtension and ClusterDeployedOperatorExtension would be even clearer?

   👍React with 👍1Reacted by Sébastien Crocquesel
3. csviri commented on May 16, 2022

   

   csviri

   on May 16, 2022

   Collaborator

   More actions

   I'm personally fine with both, current state (for me sounds expressive enough), also these new ones sounds good.
4. laxmikantbpandhare

   assigned

   csviri

   on May 26, 2022
5. laxmikantbpandhare

   added

   kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.

   on May 26, 2022
6. metacosm

   added this to the 3.1 milestone on May 31, 2022
7. metacosm

   assigned

   metacosm

   and unassigned

   csviri

   on May 31, 2022
8. metacosm

   added 3 commits that reference this issue on May 31, 2022

   refactor: rename JUnit extensions to be more explicit

   ...

   This issue will close once commit 326ba56 is merged into the 'main' branch.

   326ba56

   refactor: rename JUnit extensions to be more explicit

   ...

   This issue will close once commit ce25c16 is merged into the 'main' branch.

   ce25c16

   refactor: rename JUnit extensions to be more explicit (#1254)

   ...

   This issue will close once commit 495220c is merged into the 'main' branch.

   495220c
9. csviri

   added 3 commits that reference this issue on Jun 1, 2022

   refactor: rename JUnit extensions to be more explicit (#1254)

   ...

   This issue will close once commit 2a41476 is merged into the 'main' branch.

   2a41476

   refactor: rename JUnit extensions to be more explicit (#1254)

   ...

   This issue will close once commit 83ed3c2 is merged into the 'main' branch.

   83ed3c2

   refactor: rename JUnit extensions to be more explicit (#1254)

   ...

   This issue will close once commit 3453ec0 is merged into the 'main' branch.

   3453ec0
10. csviri

    closed this as completedon Jun 6, 2022
11. csviri

    added 2 commits that reference this issue on Jun 7, 2022

    refactor: rename JUnit extensions to be more explicit (#1254)

    ...

    This issue will close once commit 3026876 is merged into the 'main' branch.

    3026876

    refactor: rename JUnit extensions to be more explicit (#1254)

    ...

    This issue will close once commit 8b38c92 is merged into the 'main' branch.

    8b38c92
12. csviri

    added a commit that references this issue on Jun 17, 2022

    refactor: rename JUnit extensions to be more explicit (#1254)

    ...

    This issue will close once commit 101d644 is merged into the 'main' branch.

    101d644
13. csviri

    added 11 commits that reference this issue on Jun 27, 2022

    refactor: rename JUnit extensions to be more explicit (#1254)

    ...

    This issue will close once commit 80dc74e is merged into the 'main' branch.

    80dc74e

    refactor: rename JUnit extensions to be more explicit (#1254)

    ...

    This issue will close once commit 64c7330 is merged into the 'main' branch.

    64c7330

    refactor: rename JUnit extensions to be more explicit (#1254)

    ...

    This issue will close once commit bee5b89 is merged into the 'main' branch.

    bee5b89

    refactor: rename JUnit extensions to be more explicit (#1254)

    ...

    This issue will close once commit 9e1da72 is merged into the 'main' branch.

    9e1da72

    refactor: rename JUnit extensions to be more explicit (#1254)

    ...

    This issue will close once commit 6d9ace6 is merged into the 'main' branch.

    6d9ace6

    refactor: rename JUnit extensions to be more explicit (#1254)

    ...

    This issue will close once commit caf12d5 is merged into the 'main' branch.

    caf12d5

    refactor: rename JUnit extensions to be more explicit (#1254)

    ...

    This issue will close once commit ea331e6 is merged into the 'main' branch.

    ea331e6

    refactor: rename JUnit extensions to be more explicit (#1254)

    ...

    This issue will close once commit 919d573 is merged into the 'main' branch.

    919d573

    refactor: rename JUnit extensions to be more explicit (#1254)

    ...

    This issue will close once commit 53cbd95 is merged into the 'main' branch.

    53cbd95

    refactor: rename JUnit extensions to be more explicit (#1254)

    ...

    This issue will close once commit f0dd210 is merged into the 'main' branch.

    f0dd210

    refactor: rename JUnit extensions to be more explicit (#1254)

    ...

    This issue will close once commit d4c469c is merged into the 'main' branch.

    d4c469c