Views sort WorkflowState by Weight (D8)

You might want to add a relation to the states.

hi @johnv. thank you for your time, but that suggestion doesn't work for the use-case initially defined:

- I have a workflow with states. And that states can haver an order defined by weight
/admin/config/workflow/workflow/my_wf/states

- I would like to build a view where the content is sorted using states weight and not states title

Using a relationship, I can only relate to workflow_transition, and that won't work since I don't have weight in there.

So what would work is a relation to the config since states are configs and not entity... in theory.

Is this module of any use? :
Views Sort By Options Weight →

I haven't checked it, but I may incorporate it.

I have tested that module, and also checked the source code, and that is very hard do extend.

We would need to patch it very hard in order to get "set weight", since it's not pluggable.

To that kind of work, it would be preferable to make a new View sort handler specific to workflow.

namespace Drupal\workflow\Plugin\views\sort;

use Drupal\views\Plugin\views\sort\SortPluginBase;

and then explore from here.

I don't know workflow module to make this work quickly. What do you think about this approach?

Yes, I have checked that too.
It seems best to indeed create a custom sort handler.
Not sure if I will start on this soon, since I am cleaning up the big openissue list ATM.

A file needs to be copied from views module, into \workflow\src\Plugin\views\sort.
It should read all config transitions or config states, then sort on weight.

When you do sorting, it would be nice if the workflwo type is fetched also, since there are issues with multiple workflows.

Please check if this issue is a duplicate of ✨ Views sort WorkflowState field by Weight/Label Active if so, let's continue over there.

I will try and see if a views sort handler can be done here, and thank you for your reply.

I have checked the other issue, and I think the OP is having problems in using multiple tables that come from distinct views blocks, and he has problems in sorting the columns.

here the problem is not specific to Table but views in general, where we don't have the handler available.
So I would keep it separate, if you don't mind.