![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Changes between Version 1 and Version 2 of Ticket #61269, comment 32
- Timestamp:
- 05/24/2024 02:43:43 PM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #61269, comment 32
v1 v2 1 While I appreciate the consideration and use cases, I thinking all of the scenarios presented are achievable with the current design of one entry `url`.1 While I appreciate the consideration and use cases, I thinking all of the scenarios presented (except for a maybe 4th step) are achievable with the current design of one entry `url`. 2 2 3 3 Then if later in the future, more use cases are discovered that require different consideration, such as the ability to disable all onboarding, how to achieve those can be explored, e.g. adding another filter. 4 4 5 5 For this phase, I agree with @costdev. The configuration data he proposes fits today and the future's intent and needs. 6 7 That said, if there's a real world case and strong possibility of adding a 4th to the plugin install > activate > onboard workflow, then that might be a reason to rename it `onboarding_url`.
