-
Notifications
You must be signed in to change notification settings - Fork 14
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
Support Locust >=1 #71
Conversation
🤖 zincr found 0 problems , 1 warning
Details on how to resolve are provided below Large CommitsChecks all commits for large additions to a single file. Large commits should be reviewed more carefully for potential copyright and licensing issues This file contains a substantial change, please review to determine if the change comes from an external source and if there are any copyright or licensing issues to be aware of
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting approach with the aliases. I like how little code needs to be changed because of it!
Thank you 😊 |
Adds support for the new major version of Locust (
locust=~1
) in generated locustfiles.Related to #69.
Description
In generated locustfiles, detect the major version of the corresponding
locust
package; if that version is 1:tasks
field instead of thetask_set
field (that triggers a deprecation warning in 1.0).Types of Changes
What types of changes does your code introduce? Keep the ones that apply:
TODO
List of tasks you will do to complete the PR:
Review
Reviewers' checklist:
good tests for these flows?
If this PR rather removes flows, are the obsolete tests removed as well?
technical (in source files) and functional (under
docs/
) documentation.In doubt, refer to https://semver.org.