-
Notifications
You must be signed in to change notification settings - Fork 5
Conversation
Before going any further, it seemsthat the javascript behavior is not implemented here. We should have the same beahvior here. |
@emeryro |
@hapertown I'll come back to you with a solution for that ;) |
@hapertown I've added the JS behavior. It's not as straightforward as I hoped but at least it's working (see https://github.com/ec-europa/ecl-twig/pull/37/files#diff-b2d39af2fbd791ba86ecf4cb6a737e0fR81) You don't have to do anything regarding the JS behaviour for the component, it's done. In the future, I might come back with a better solution. @emeryro I guess you can review this PR now |
Dear all, the javascript behavior works well now. I quickly checked the other basics and didn't find any issues. |
'simple', | ||
() => | ||
breadcrumb({ | ||
links: [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When possible, please use the data from the spec component. That way, if we change data on ECL for whatever reason it will be updated everywhere.
You will probably have to map the structure of ECL data with yours, as it has been done here or here for instance.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in cbbfd67
Yes, please update it here. |
Updated in 92da83b |
PR description
Please drop a few lines about the PR: what it does, how to test it, etc.
QA Checklist
In order to ensure a safe and quick review, please check that your PR follow those guidelines:
devDependencies
devDependencies
include
orembed
) asdependencies
@ecl-twig/ec-components
'sdependencies
yarn.lock
contains changes, I have committed itpr: review needed
to indicate that I'm done and now waiting for a review ,pr: wip
to indicate that I'm actively working on it ...)