vedantprajapati commented on PR #33040:
URL: https://github.com/apache/superset/pull/33040#issuecomment-2787524787

   > > We also need to think how things will work when the values differ 
between selected assets.
   > 
   > To keep it simple, I'd vote for a one-operation-per-assignment approach, 
so for owners the user would check a set of dashboard and assign owners to 
them, one operation per set of owners.
   > 
   > Note that it could be great to have multiple actions here `Add Owners`, 
`Set Owners`, and potentially `Remove Owners`.
   > 
   > Most CRUD framework offer this kind of functionality to some degree. Would 
be great if we can reuse Actions across entities too where that makes sense. 
Owner-management being a common use case here, where in theory could be backed 
by reusable stuff in the frontend/backend, like Mixins on `Model` and `RestApi` 
objects.
   
   so for now, I can rename this button to Set Owners then?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to