-
-
Notifications
You must be signed in to change notification settings - Fork 55
Custom Page Prefix Usability Fixes #2736
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
Conversation
- automatically compute prefix from starting URL, if no other prefix is set in custom prefix mode - add '^' to each custom prefix URL, as it is a regex - rename 'Extra URL Prefixes' to just 'URL Prefixes' and adjust help text to indicate that the prefix list is the list that is in scope - fixes #2735, follow up to #2722
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.
Makes sense and testing well. I added a commit to update the user guide documentation appropriately.
I think these changes are also safe in terms of not breaking existing workflows, since existing custom page prefix workflows created before these changes (e.g. those set on a schedule to run periodically) will still have the "prefix" scopeType set for the first seed, and only new Custom Page Prefix workflows will be affected.
Co-authored-by: sua yoo <sua@webrecorder.org>
- ensure auto-added '^' is stripped from custom prefix URLs loaded from db
- follow-up to: #2736: remove '^' custom prefix URLs to avoid accumulating '^' via utility function - Show URL prefix list in settings for custom prefix scope. - Update user guide with correct custom prefix field. --------- Co-authored-by: sua yoo <sua@webrecorder.org>
Examples
The following examples demonstrates the new behavior, auto-populating the URL Prefix field:
custom-prefix.mp4
Makes it easy to then adjust the prefix to a subpath instead:
custom-prefix-2.mp4