Open pscadding opened 1 month ago
Also I wonder if the setting name should not be my tasks specific and then you list the tab under it. That way if we add the sort field to other tabs we wont need to change the setting name.
Is it possible to invest more time for it?
I've spent some more time today, and if I modify SG utils I can catch the error, and raise it as a signal
I am nervous about this though, I'm not sure if this will negatively impact other tools using the SG Utils.
I've created a PR for that here: https://github.com/shotgunsoftware/tk-framework-shotgunutils/pull/158
We decided not to implement the changes on the SG Utils for better catching. We didn't want to introduce unnecessary risk for the handling of this edge case.
Makes the My Tasks tab sort fields configurable through the yml settings.
The user can choose any fields including linked fields to sort by, assuming that they are valid fields to sort by.
The default sort options are the same as before + the step which appeared to be mostly added by possibly accidentally excluded. (Note the UI styling looks a little weird here, because I'm running out of my terminal and not a DCC)
The user can then customise the list through the env config.
If its configured with a non existing field it will result in an error in the console if the user picks that sort field in the list. I'm not sure there is a better way of handling this as it asynchronous so I can't just wrap the instruction to load data in a try except. I think in order to get a better handle on it we might need to make changed to the shotgun model. An example of the error you would get is here: