petrbroz / bim360-issue-editor

Prototype application for bulk-editing BIM 360 issues using Autodesk Forge APIs.
https://bim360-issue-editor.autodesk.io
MIT License
9 stars 11 forks source link

Wish: users in the project #6

Open xiaodongliang opened 4 years ago

xiaodongliang commented 4 years ago

It is a limitation of current API that we cannot GET Project Users, but I would suggest the workflow check User @ Me to get if a user has permissions of Issue. It more or less helps. https://forge.autodesk.com/en/docs/bim360/v1/reference/http/users-me-GET/ I was trying to update with a non-project member, but because of the other issue, I have not yet seen what would happen. https://github.com/petrbroz/bim360-issue-editor/issues/5

xiaodongliang commented 4 years ago

just appending the comments replied in email for this point: Issue permissions of a user will affect the behavior of API. e.g. if a user has View permission only, API cannot Post/Patch issue with his 3LO token. Container: users/me will tell permission in quality_issue, though not all are same to UI configuration, e.g. View only will return empty quality_issue json, but it can be a workaround to know the permission, because in default a project member in issue module will have view permission on Issue. So empty quality_issue json could mean View only.

If it is not project member, this endpoint will return 401. This is why I suggested adding one section to check the project member instead of listing all account users in the option

petrbroz commented 4 years ago

Btw. I've added code that disables different UI inputs based on the issue.permitted_attributes parameter. Would that address your request here?