Skip to content

Conversation

@unaiberis
Copy link

No description provided.

Copy link
Contributor

@oihane oihane left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@pedrobaeza pedrobaeza added this to the 16.0 milestone Apr 2, 2025
string="Type"
name="type"
string="Category"
name="category"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't change this identifier, as it can be used in children modules.

Copy link

@anajuaristi anajuaristi Oct 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pedrobaeza The module has an issue. It has been incorrect from begining and it's quite confusing for users.
The string and name is TYPE but group_by is by categ_id. When they group by type they don't understand the behavior since the field "type" exists on claims and it's added by this module.
It should be consistent. Category should group by category and type should group by type.
We are trying to change this months ago and it seems it's not going to be merged since our PRs are being closed everytime.
Please tell us how we must propose the PR to be merged.

We only want to be consistent behavior on both claim fields
Thank you!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It has nothing to do with that, Ana. It's a question on stability. If you change the internal name, some modules will stop working. Just change the label, and for the user, the issue will be resolved.

@github-actions
Copy link

github-actions bot commented Aug 3, 2025

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 3, 2025
@github-actions github-actions bot closed this Sep 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved stale PR/Issue without recent activity, it'll be soon closed automatically.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants