Feat/df 1068: Add 'offline' filtering option

[jbarnsley10]

Ticket DF-1068

[Copilot]

Pull request overview

Adds an "offline" option to the forms library status filter and surfaces an Offline tag in the form-status component. A new FormFilterStatus enum is introduced (alongside the existing FormStatus) so that the filter type can include offline without altering the runtime status type, and the Joi search schema and SearchOptions type are updated accordingly. Existing tests are migrated from FormStatus to FormFilterStatus.

Changes:

• Introduce FormFilterStatus enum (draft, live, offline) and use it in SearchOptions.status and the search Joi validator.
• Render an "Offline" tag in the form-status template when metadata.offline is set, and sort the status checkboxes alphabetically in the search component.
• Update designer test files to import and use FormFilterStatus instead of FormStatus.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
model/src/common/enums.ts	Adds new FormFilterStatus enum including Offline.
model/src/common/search/types.ts	Switches SearchOptions.status to FormFilterStatus[].
model/src/common/search/index.ts	Allows 'offline' in the status Joi validator.
designer/server/src/common/components/form-status/template.njk	Adds Offline tag and new conditional branches based on metadata.offline.
designer/server/src/common/components/search/template.njk	Sorts status checkboxes alphabetically.
designer/server/src/lib/forms.test.js	Updates type references to FormFilterStatus.
designer/server/src/models/forms/library.test.js	Updates type references to FormFilterStatus.
designer/server/src/routes/forms/library.test.js	Updates type references to FormFilterStatus.

Comments suppressed due to low confidence (1)

designer/server/src/common/components/form-status/template.njk:17

• When params.metadata.offline is true and the form has a live state, only the Offline tag is rendered and the Live tag is dropped, but when offline is combined with draft the Draft tag is still shown alongside Offline. This is asymmetric and means a viewer cannot tell that an offline form was previously published live. Additionally, if offline is true but neither draft nor live is set, the conditional falls through to the final else branch and renders a "Draft" tag, which is misleading. Consider rendering Offline as an additive tag (similar to Draft) rather than a replacement, and handling the offline-only fallback explicitly.

{% if params.metadata.offline and params.metadata.draft | length %}
  {{ tagDraft }} {{ tagOffline }}
{% elseif params.metadata.offline and params.metadata.live | length %}
  {{ tagOffline }}
{% elseif params.metadata.draft | length and params.metadata.live | length %}
  {{ tagDraft }} {{ tagLive }}
{% elseif params.metadata.live | length %}
  {{ tagLive }}
{% else %}
  {{ tagDraft }}
{% endif %}

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud