Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename Workflow Class #21

Open
ms-k1ngk0ng opened this issue Oct 26, 2022 · 1 comment
Open

Rename Workflow Class #21

ms-k1ngk0ng opened this issue Oct 26, 2022 · 1 comment

Comments

@ms-k1ngk0ng
Copy link
Contributor

As pointed out, Workflow means something specific and naming a class with this will make things increasingly more confusing.

@ms-k1ngk0ng
Copy link
Contributor Author

ms-k1ngk0ng commented Nov 18, 2022

This one is pretty self-explanatory. I was taking the term blueprint out for a spin and may have merged some commits that use it as a replacement for workflow. But, ultimately it's going to be up to y'all. I think what is most important is using a word that emphasizes the spirit of what the workflow is doing -- it's essentially a boiled-down encapsulation of all that the TestScript achieves. If there's a setup, and if that setup requires storing the response in order to then grab the id from that response, then that's shown in the workflow.

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

No branches or pull requests

1 participant