-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Remove legacy UI #2703
Remove legacy UI #2703
Conversation
andrewbaldwin44
commented
May 6, 2024
•
edited
Loading
edited
- Remove words "legacy" and "modern" from codebase as we only have one UI now
- Remove legacy-ui and modern_ui flags
- Remove logic for rendering legacy UI
- Remove templates and static assets for legacy UI
- Update UI tests to suit the modern UI
- Update documentation to only include logic for modern UI
- Ensured modern UI, web login, HTML report, and downloaded HTML report all continue to work as expected
1778381
to
f9fe009
Compare
Nice! Can we keep the argument around (and hide it using help=configargparse.SUPPRESS), and exit with an error message if someone sets it? |
2e7577d
to
2294b2f
Compare
locust/main.py
Outdated
@@ -183,7 +179,8 @@ def is_valid_percentile(parameter): | |||
options.spawn_rate = options.hatch_rate | |||
|
|||
if options.legacy_ui: | |||
sys.stderr.write("[DEPRECATED] The legacy UI is deprecated and will be removed soon\n") | |||
sys.stderr.write("[DEPRECATED] The legacy UI is deprecated") |
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.
I think "deprecated" usually means "going to be deleted, but still works", so this line is confusing :)
) | ||
self.assertRegex(response.text, re_spawn_rate) | ||
self.assertNotRegex(response.text, re_disabled_spawn_rate) | ||
|
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.
These regex tests are being removed because they are covered by our frontend tests
self.assertEqual( | ||
self.environment.available_user_classes["User1"].json(), | ||
{"host": "http://localhost", "tasks": ["my_task_2"], "fixed_count": 0, "weight": 1}, | ||
) |
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.
These tests were just moved to join the base Web UI tests
LGTM. Especially if you add I'll want to hold off a day or two on merging though, because I'd like to release the changes already merged as a separate release. |
Nice! |