Skip to content

[feature] be able to give an order to execute the group #3728

@dev-a

Description

@dev-a

Hello
I'm not sure if it's a bug or a feature, but yesterday I got an unexpected result.

Let's imagine that I decided to create three groups/tags:
title, heading, and content.
Each has a filter: title, h1, .content.

The ‘title’ group was assigned the ID
c585afff-5ef8-4abb-ad40-42fd9d3d9058.
The ‘h1’ group was assigned the ID
adf285f5-3de2-4dd7-a212-4478331ac388
The ‘content’ group was assigned the ID
4be004ec-3b86-48e0-a26b-e60244d6f6f3

I added the following tags to my “watch” in this order:
title, heading, content

However, clearly
at the time of notification
it will first give me
‘content’
then ‘heading’
and finally ‘title’

which is not logical in this case XD

I understand the problem: it must sort according to the ID to determine the order rather than using the order of the tags on the watch.

A little bonus:
I've deleted a group by mistake quite a few times while testing this thing. There should be a “Are you sure you want to delete?” prompt when the group isn't empty.

PS: Congratulations on the latest release, it seems to have a lot of interesting features.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions