🇫🇷France @goz

goz → created an issue.

goz → created an issue.

issue triage

Thank you for your work

i agreed this should be the default behaviour, so i change it in this way and add tests

goz → made their first commit to this issue’s fork.

Thank you for your contribution.

I update MR to follow your suggestion, but force $regions to be reinitialized for each section. Otherwise, components could be duplicated in different sections. I have this issue using 2 sections of ui_suite_bootstrap:grid:row_1, the second one has also blocks from the first one.

By the way, please, do not use anymore patches when MR is opened, or at least use interdiff like before. It's pretty hard to figure out differences between your patch and MR

Based on patch #4, i improve this adding a batch_size and start_at row settings, so we can choose during import how many rows to import by batch, and where to start in file. Still assuming the first row is used as header.

I rework the way the batch works, because in my case, with a large file (+20Mo, +10k rows), i have a max_allowed_packets error. Before launching the batch, the entire CSV file was loaded and some preprocess done.
Now, only the number of rows specified by the batch sized are loaded.

goz → made their first commit to this issue’s fork.

goz → created an issue.

I have 2 fields in a paragraph with this widget :

• Field A limited to 1 item. Autocomplete works and buttons display
• Field B limited to 3 items. Autocomplete ajax is called but result does not diplay, nor buttons.

I add display_remove_button settings in condition to be able to display buttons. Otherwise, following settings does not allow to display button during edition.

goz → made their first commit to this issue’s fork.

Error disappear after applying patch in #24
Thanks !

Remove Future Friendly website link, which is now a promotion website to bet

goz → created an issue.

goz → created an issue.

phenaproxima → credited goz → .

goz → created an issue.

Thank you for your quick answer.
I effectively saw this logic (from code and tests). That's why i suggested to add in description a warning that a default value should be defined in case required was originally TRUE.

Can you at least check "required" works ? As i explain in the issue, !empty($settings['required']) will always return FALSE except if there is no required key in the array, so definition will never be overriden.

goz → created an issue.

My bad, everything is working as expected.
Some debug from another issue which has nothing with layout paragraph had mess this up.

goz → created an issue.

A duplicate page exists with informations

goz → made their first commit to this issue’s fork.

goz → created an issue.

I have know no errors on display, but can only have one cell/field in a row (here title)

May be i'm wrong, here is how i configure my view :

Format with table component, display cell component

Format settings :

Display settings, i cannot configure to display the rendered field without defining a specific field

In any case, submitting generate an error

InvalidArgumentException: "component_id" is an invalid render array key. Value should be an array but got a string. in Drupal\Core\Render\Element::children() (line 97 of core/lib/Drupal/Core/Render/Element.php).

Drupal\Core\Render\Renderer->doRender() (Line: 222)
Drupal\Core\Render\Renderer->render() (Line: 491)
Drupal\Core\Template\TwigExtension->escapeFilter() (Line: 194)

By default with component integration in views, i cannot produce a working view with table/cell component. Some errors occures

I have the same issue with Feeds module 🐛 When using Navigation module, Save button doesn't trigger Active which display dropbutton actions when editing a feed content. In this case, dropbuttons are displayed, but not actions on click.

I have the same issue, except i have no "Enable sticky action buttons" in Gin settings when navigation module is enabled. Disabling navigation module show the option, but it's not checked.

Using Claro as admin theme, dropbuttons are no more sticky in header.

So it's an issue with Gin when navigation module is enabled and dropbuttons are used in actions.

Drupal: 11.2.2
Gin: 5.0.3
Feeds : 8.x-3.0

goz → created an issue. See original summary → .

goz → created an issue.

goz → created an issue.

I work on top of Mikael work on his MR.

I add the cell component.

Remove row and cell attributes which are not defined by dsfr.
Cell attributes are now directly managed by cell component.

Provide 3 stories :

• Preview
• Fixed headers (but with dsfr, only column can be fixed)
• Alignments (vertical and horizontal)

Unfortunatelly, i have no tools right now to encode story to YAML in twig. Twig does not provide this feature (it's part of symfony/twig-bridge)

And i don't think it's a good idea to try to add this from stories component or another preprocess.

Here is an example with JSON format, even if i know it's not the best format.

Display with components is here, we still have to define how display the "code" part.

Looking at tabs story, id key is wrong. Should not be unique_id but id.

goz → created an issue.

pdureau → credited goz → .

This is how this code will display a story with its json settings :

Goal should be to look like dsfr does :

They are using prismsjs to display html, may be we can use it to display a clean json ?

I love the "show code", but that can be a button, a tab or whatever.
I don't think it's a good thing to display code by default, display is already huge, we should not add large piece of code which is not relevant at first.

When i see a display i want, only at this moment, i want to know how to build it, so i click on the "show me how to do" thing.

Unfortunatelly, there is no component in dsfr to display code or make this feature.

DSFR give us :

• Modal
• Accordion
• Tab
• Transcription

May be we could us one of them ?

Here is an example based on transcription (but we cannot change "transcription" text):

So much better !
Here is the compact display

When display is in modal, clicking on radio change the preview radio status, not the one in the modal.

This is caused by the fact we display two form display.

If it's possible by the dsfr library, we should have two distinct event displays OR an action on one should dispatch on all

See video →

Nice, it's more understandable.

Use library_wrapper to display variations in a grid, like it's done in 📌 Add new stories: Card Active

Jean is already on it

Jean is working on it, so i remove assignation

I thought about a story to show how the pagination will display in case we are in the last page (next page link and last page link are disabled).

I agree that this is really a minor feature.

Modal with display works as expected.

But, i think this story should be placed in display component, not in modal. This is a way to implement a 'display' component and is not relevant by the modal component itself.

Looks good to me, display as expected.

Compact display in /admin/appearance/ui/components#ui_suite_dsfr:tile is not the best display, but this should be dealed in specific issue

Type button was ready everywhere excepts for tag component.

I disagree, ui_suite_bootstrap implements icons thanks to .icons.yml file, same as the icons libraries you mention.

I have the same issue with ui_icons_drupal.

Debugging, i can confirm the first time i display input an type text, no JS is loaded nor called.

See https://www.drupal.org/files/issues/2025-07-13/display-builer-icons-no-j... →

goz → changed the visibility of the branch 3531467-1.0.0-alpha1-navigation-left to hidden.

Converting SASS to pure CSS does not change anything

.display-builder .db-form * {
  font-size: var(--sl-button-font-size-medium) !important;
}

.display-builder .db-form .shoelace-tabs {
  margin-bottom: 0.5rem;
}

.display-builder .db-form .ui-icons-wrapper  .ui-icons-select {
  display: inline-block;
  margin-top: 0.5rem;
}

.display-builder .db-form .ui-icons-wrapper  .ui-icons-select .form-item--error-message {
  display: none;
}

.display-builder .db-form .ui-icons-wrapper  .ui-icons-select > div {
  display: contents;
}

.display-builder .db-form .ajax-progress-throbber {
  display: none !important;
}

.display-builder .db-form .ui-icons-settings-wrapper {
    margin-top: 0.5rem;
}

Moving back to https://git.drupalcode.org/project/display_builder/-/blob/4b188bc51d868a... is OK

goz → created an issue.

Everything seems to be fine with 47f82bb1 commit on #3529103, comment #31.

I start from 47f82bb1 commit, rebase on 1.0.x branch, and still no bug

BUT testing from commit 7b31071a is broken

goz → created an issue.

goz → created an issue.

goz → created an issue.

goz → created an issue.

goz → created an issue.

By default, we have only one story by component, and display variants.

Can we define variants and props on which to loop to define stories ?

goz → created an issue.

pdureau → credited goz → .

Sorry for the false positive, i forgot to remove some tests in core which make my instance not relevant.
I spend a big part of my weekend on it... and burn too much neurons.

Finally, took less time this afternoon to fix it once i reproduce again.

I have no warnings :/

Can you give me more informations to reproduce ?

Which theme do you use, do you start from a fixture, on which component ?
May be a screencast will help

Thanks