You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reading the documentation I noticed that there are a lot of potential marker names including run(), and even custom markers proposed in #10. It seems like this has the potential to result in confusing code. Say for instance that some one is new to a project and doesn't know about pytest-ordering. What does the run marker do? Run is a very ambiguous word. I would like to suggest choosing a more specific name. As an option order might be a more intuitive name for someone reading code. The marker signature might look like this: order(pos=None, before=None, after=None).
The text was updated successfully, but these errors were encountered:
I've updated the title to describe the proposal. I think a single marker name that takes parameters is a good idea -- though I'm interested to hear feedback from folks if you agree or disagree.
Reading the documentation I noticed that there are a lot of potential marker names including run(), and even custom markers proposed in #10. It seems like this has the potential to result in confusing code. Say for instance that some one is new to a project and doesn't know about pytest-ordering. What does the
run
marker do? Run is a very ambiguous word. I would like to suggest choosing a more specific name. As an optionorder
might be a more intuitive name for someone reading code. The marker signature might look like this:order(pos=None, before=None, after=None)
.The text was updated successfully, but these errors were encountered: