Skip to content

Conversation

@MyvTsv
Copy link
Contributor

@MyvTsv MyvTsv commented Jan 6, 2026

  • I have performed a self-review of my code.
  • I have added tests (when available) that prove my fix is effective or that my feature works.
  • I have updated the CHANGELOG with a short functional description of the fix or new feature.
  • This change requires a documentation update.

Description

  • It fixes !41257
  • In the version of the plugin compatible with GLPI 11, the Visibility (is_private) field now uses a dropdownYesNo.
    This change results in a loss of clarity compared to the GLPI 10-compatible version, where this field was represented by a dropdownArrayField with the options Public/Private.

The Yes/No choice does not clearly reflect the concept of model visibility.

Screenshots (if appropriate):

GLPI 10:
image

GLPI 11 before fix:
image

GLPI 11 after fix:
image

@MyvTsv MyvTsv self-assigned this Jan 6, 2026
@MyvTsv MyvTsv marked this pull request as ready for review January 6, 2026 10:45
@MyvTsv MyvTsv requested review from Rom1-B and stonebuzz January 6, 2026 10:45
{{ fields.textField('name', values['name'], __('Name'), field_options) }}

{{ fields.dropdownYesNo('is_private', values['is_private'], __('Visibility'), field_options) }}
{{ fields.dropdownArrayField('is_private', values['is_private'], {
Copy link
Contributor

Choose a reason for hiding this comment

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

I would just have changed the label to “Is Private,” for example, to keep the dropdownYesNo() type.

@MyvTsv MyvTsv requested review from Rom1-B and stonebuzz January 7, 2026 08:49
@stonebuzz stonebuzz merged commit 0b9381f into pluginsGLPI:main Jan 7, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants