Open elias-ba opened 2 weeks ago
@elias-ba My recommendation for this will be to default to the latest version of the workflow rather than showing the user a 404 page. The users don't know about the lock version and showing them a 404 does not help them debug the issue.
@christad92 good point, but the only reason why I still think it's a 404 is because all of this is happening thru the URL. If we decide to default to the latest version we would be deciding to serve the user something they didn't order at all. It looks to me like I order a Bouye, and you don't have a Bouye and you serve me a Vodka. The muslim of me would be very angry 😆. Anyway I really think when the user types a non existent lock_version we should just say no ressource is associated to this URL. @taylordowns2000 @stuartc what you guys think ?
Agreed. Forgetting costs for a second and trying to bring together some valid points from Stu, Elias, and Ayo:
s="123"
where there is no job "123" to show should load the canvas with no open panel.)Either way, i'd put this fairly low on the backlog
When visiting the workflow edit page, one can pass a URL parameter to control the loaded snapshot version. That parameter is
v
, and it expects a positive integer value. That value is then queried in the database to find the associated workflow snapshot. When no snapshot is found, the app crashes. Instead of the app crashing we should return a 404 page.