Problem Description
When the application list falls back to the chat-log permission branch, it returns a malformed route:
/application//workspace${item.id}/${item.type}/chat-log
This does not match the registered application detail route /application/:from/:id/:type.
Code Location
ui/src/views/application/index.vue:737
- Matching route definition:
ui/src/router/modules/application-detail.ts:8
Steps to Reproduce
- Use an account/role that can read an application chat log but does not satisfy the earlier overview/edit/access/chat-user permission branches in
getApplicationUrl.
- Open the application list.
- Click the application card/list item.
Actual Result
The generated URL is shaped like:
/application//workspace<application_id>/<type>/chat-log
The path has an extra / after application and misses the / between workspace and the application id, so it cannot match the expected route.
Expected Result
The fallback chat-log URL should be:
/application/workspace/${item.id}/${item.type}/chat-log
MaxKB Version
Current v2 branch.
Problem Description
When the application list falls back to the chat-log permission branch, it returns a malformed route:
/application//workspace${item.id}/${item.type}/chat-logThis does not match the registered application detail route
/application/:from/:id/:type.Code Location
ui/src/views/application/index.vue:737ui/src/router/modules/application-detail.ts:8Steps to Reproduce
getApplicationUrl.Actual Result
The generated URL is shaped like:
/application//workspace<application_id>/<type>/chat-logThe path has an extra
/afterapplicationand misses the/betweenworkspaceand the application id, so it cannot match the expected route.Expected Result
The fallback chat-log URL should be:
/application/workspace/${item.id}/${item.type}/chat-logMaxKB Version
Current
v2branch.