IBX-11413: Use design-system dropdown component - #1902
Conversation
4f5430d to
8193ee5
Compare
8193ee5 to
c41218f
Compare
c41218f to
3f5f8e4
Compare
3f5f8e4 to
1f7c8fa
Compare
|
cbc8bf3 to
1fe890c
Compare
|
| "repositories": [ | ||
| { | ||
| "type": "vcs", | ||
| "url": "https://github.com/ibexa/design-system-twig" |
There was a problem hiding this comment.
This is probably not needed.
f474be6 to
ed8b2e2
Compare
6ea5c67 to
1f8c649
Compare
98c70f4 to
b7d4154
Compare
| import { | ||
| DropdownMultiInput, | ||
| DropdownSingleInput, | ||
| } from '../../../../../../../design-system-twig/src/bundle/Resources/public/ts/components/dropdown'; |
There was a problem hiding this comment.
Don't we have alias for this bundle?
If we don't we probably should. :D
| }; | ||
| const attachFieldDefinitionNodeEvents = (fieldNode, { targetContainer }) => { | ||
| const initDropdown = (dropdownContainer) => { | ||
| const dropdownAlreadyInitialized = !!ibexa.helpers.objectInstances.getInstance(dropdownContainer); |
There was a problem hiding this comment.
Not for this PR, but considering we're introducing TS in 6.0, do we want to create separate hasInstance in order not to cast it to bool each time?
| const clearSection = (event) => { | ||
| sectionSelect[0].selected = true; | ||
| if (sectionSelect) { | ||
| sectionSelect[0].selected = true; |
There was a problem hiding this comment.
| sectionSelect[0].selected = true; | |
| sectionSelect?.[0].selected = true; |
nitpick from optional chaining apostle ;)
There was a problem hiding this comment.
conditional chaining cannot be used in assignment :)
This reverts commit 9eaad2c.
The order inputs in relation_base.html.twig use ids-input-text markup for styling only, without the actions block and clear button. The global init_components.ts picked them up and InputTextInput threw on the missing elements, aborting the rest of the layout bundle (ibexa.core.Backdrop and everything after it) on edit pages with existing relations. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
IBX-12038 replaced both selectors with the same .ids-btn--extra-actions class, leaving pages whose trigger buttons still use .ibexa-btn--extra-actions (site-context, customer templates) unable to open the extra actions panel. Restore the dual selector. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Wrap over-length lines flagged by prettier in files touched by the DS dropdown migration; no logic changes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
61b9622 to
bf44414
Compare
Address review remark: replace the deep relative design-system-twig import with the existing @ibexa-design-system alias, as used elsewhere. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The trans wrapper contained a Translator.trans(key, ...) call with a non-literal key, which crashed the JS translation extractor (and the TranslationTest integration suite) on Peast Identifier::getValue(). Passing the Translator object as the context value removes the call site entirely; DS components invoke it method-style, so binding and behavior are unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The DS dropdown wrapper introduces the ibexa.dropdown.placeholder.all key in the ibexa_design_system_twig domain; ship its extracted xliff so the translation test passes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|



Description:
For QA:
Documentation: