Add user preference for the missing visible signature warning #8322

Context

Part of #8321.

LibreSign will warn a requester when one or more signers have no visible signature field.

The requester can choose not to see this warning again.

LibreSign already has a generic API to save user configuration. This issue only needs to add the new preference to the existing user configuration flow.

Preference

Add this user configuration key:

warn_without_visible_signature_fields

The value controls only whether the warning is shown.

Expected values:

• 1: show the warning;
• 0: do not show the warning.

When the user has no saved value, the default must be 1.

This preference must not change signature fields, signature positions, requests or signing behavior.

Backend changes

Reuse the existing endpoint:

PUT /apps/libresign/api/v1/account/config/{key}

Do not create a new controller or endpoint.

The existing endpoint already stores values for the authenticated user.

Update AccountService::getConfig() so the frontend receives:

{
  "warn_without_visible_signature_fields": true
}

when the warning is enabled, and:

{
  "warn_without_visible_signature_fields": false
}

when it is disabled.

If no value is stored, return true.

Follow the same pattern already used by boolean user settings such as:

• files_list_grid_view;
• policy_workbench_catalog_compact_view;
• policy_workbench_catalog_collapsed.

Do not add a system policy or group configuration.

Reset behavior

The existing user-config API uses an empty value to remove/reset a user setting.

For this preference, resetting the value must restore the default:

warn_without_visible_signature_fields = true

No migration is needed because this is a new preference and the default applies when no value exists.

Behat tests

Update:

tests/integration/features/settings/user-config.feature

This file already tests save, update and delete behavior for user configuration keys.

Add warn_without_visible_signature_fields to the existing CRUD scenario.

Cover:

1. save 0 and confirm the API accepts it;
2. update it to 1;
3. reset it with an empty value;
4. confirm the returned user configuration uses the default true after reset.

Keep the existing test style instead of creating a separate feature file.

If the existing scenario already covers authentication for this endpoint, do not duplicate that test only for this key.

Unit tests

Update the existing AccountService unit tests for getConfig().

Cover at least:

• stored 1 returns true;
• stored 0 returns false;
• no stored value returns the default true.

Use a data provider if it keeps these cases small and clear.

Quality

Run the related backend checks and tests.

At minimum:

• the affected PHPUnit tests;
• tests/integration/features/settings/user-config.feature;
• Psalm;
• PHPCS.

Do not change unrelated user configuration behavior.

Good first issue

This is a small backend change using an existing LibreSign user configuration API.

The main work is:

• add one user configuration key to AccountService::getConfig();
• reuse the existing /account/config/{key} endpoint;
• extend the existing PHPUnit tests;
• extend tests/integration/features/settings/user-config.feature.

No new database table, migration, controller or policy is needed.

Please follow the existing user configuration patterns and keep the change focused.

Additional context

• If you have questions, feel free to ask in this issue.
• Give a ⭐️ star to this repository if you find LibreSign useful and would like to support the project.
• You can also join our community: https://t.me/LibreSign

Done when

• warn_without_visible_signature_fields is available in user config.
• The default value is true.
• 0 is returned as false.
• 1 is returned as true.
• Resetting the stored value restores the default.
• The existing user-config API is reused.
• PHPUnit covers the value mapping and default.
• Behat covers save, update and reset.
• Psalm and PHPCS pass.