Skip to content

feat(forms): implement embeddable rendering for Fields question type - #1235

Open
alisher372 wants to merge 1 commit into
pluginsGLPI:mainfrom
alisher372:main
Open

feat(forms): implement embeddable rendering for Fields question type#1235
alisher372 wants to merge 1 commit into
pluginsGLPI:mainfrom
alisher372:main

Conversation

@alisher372

@alisher372 alisher372 commented Aug 1, 2026

Copy link
Copy Markdown

Summary

Implement the new embeddable question type interface for the Fields question type.

This allows the Fields question type to be rendered inside composite question types while keeping all rendering logic inside the Fields plugin.

What is implemented

  • implementation of the new embeddable interface;
  • embedded administration rendering;
  • embedded end-user rendering;
  • automatic block detection;
  • selection of the concrete field only;
  • reuse of the existing Fields rendering logic;
  • full compatibility with existing standalone Fields questions.

Motivation

The Fields plugin already contains all rendering logic required to display its controls.

Instead of duplicating this logic in other plugins, it is now exposed through the common interface introduced in GLPI.

This keeps responsibilities separated:

  • Fields knows how to render Fields controls;
  • composite question types only request rendering.

Backward compatibility

No existing behaviour is changed.

Standalone Fields questions continue to work exactly as before.

Related

Depends on:

Used by:

## Summary

Implement the new embeddable question type interface for the Fields question type.

This allows the Fields question type to be rendered inside composite question types while keeping all rendering logic inside the Fields plugin.

## What is implemented

- implementation of the new embeddable interface;
- embedded administration rendering;
- embedded end-user rendering;
- automatic block detection;
- selection of the concrete field only;
- reuse of the existing Fields rendering logic;
- full compatibility with existing standalone Fields questions.

## Motivation

The Fields plugin already contains all rendering logic required to display its controls.

Instead of duplicating this logic in other plugins, it is now exposed through the common interface introduced in GLPI.

This keeps responsibilities separated:

- Fields knows how to render Fields controls;
- composite question types only request rendering.

## Backward compatibility

No existing behaviour is changed.

Standalone Fields questions continue to work exactly as before.

## Related

Depends on:

- GLPI Core PR: <link>

Used by:

- Advanced Forms PR: <link>
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.

1 participant