webdev91
Online
Joined the community
07-12-2021
Level 2
Level 2
Job title here
Location here
Badges
Accepted Solutions
Likes
Posts
Discussions
Questions
Ideas
Blog Posts
Customize the badges you want to showcase on your profile
Re: Value conversion using ValueMap vs standard java methods
webdev91
Level 2
4 likes
5 posts
0 solutions
Top badges earned
View profile
webdev91
- Adobe Experience Manager
17
1
0
Likes
Total Posts
Correct reply
Hi @BrianKasingli Thank you very much for your excellent
explanation.Now, it makes sense why Adobe decided to use @ScriptVariable
in this particular Breadcrumb case, as they can handle multiple
conditions in a one-liner.
Views
Like
Replies
Re: Value conversion using ValueMap vs standard java methods
webdev91
Level 2
4 likes
5 posts
0 solutions
Top badges earned
View profile
webdev91
- Adobe Experience Manager
60
1
0
Likes
Total Posts
Correct reply
@Jörg_Hoh Thank you for your quick response.In which case we should use
@ValueMapValue over @Inject? or should we always use @Inject annotation
as a best practice?Note: I have edited my question a bit. I was talking
about @ValueMapValue annotation
Views
Like
Replies
Value conversion using ValueMap vs standard java methods
webdev91
Level 2
4 likes
5 posts
0 solutions
Top badges earned
View profile
webdev91
- Adobe Experience Manager
70
0
4
Likes
Total Posts
Correct reply
I was looking into aem-core-wcm-components GitHub repo and noticed the
different patterns for converting string to integer or boolean. Below is
the code snippet from BreadcrumpImpl.java. @ScriptVariable private
ValueMap properties; private boolean showHidden; private int startLevel;
@PostConstruct private void initModel() { startLevel =
properties.get(PN_START_LEVEL, currentStyle.get(PN_START_LEVEL,
PROP_START_LEVEL_DEFAULT)); showHidden = properties.get(PN_SHOW_HIDDEN,
currentStyle.get(PN_SHOW_...
Views
Likes
Replies
Re: Storybook and/or Component Library
webdev91
Level 2
4 likes
5 posts
0 solutions
Top badges earned
View profile
webdev91
- Adobe Experience Manager
55
2
0
Likes
Total Posts
Correct reply
Hi @milind_bachani As you mentioned, we can implement the storybook
without AEM dependency, and that's what I am doing right now. I am
creating stories for a custom component by copying HTML code from
publish mode and adding controls to a story to make it more
interactive.I was just confused with the line mentioned in the doc that
is "...you can install it and store your Storybook artifacts within the
ui.frontend module. Then, when ready for testing within AEM, they can be
deployed as ClientLibs...
Views
Likes
Replies
Storybook and/or Component Library
webdev91
Level 2
4 likes
5 posts
0 solutions
Top badges earned
View profile
webdev91
- Adobe Experience Manager
76
0
2
Likes
Total Posts
Correct reply
I am looking for a solution to document a custom component, more like a
Component Library or Storybook for the author team and developers.
Searching for the same, I came across the ui.frontend module guide on
experience league. The first thing is regarding Component Library, it
has mentioned that "we could use Component Library and work at the
component level rather than the page level." Is there any document/guide
that shows how to implement this?Link to section Using Webpack Static
Development...
Views
Likes
Replies
Community
Resources
Adobe account
Change language
Copyright © 2022 Adobe. All rights reserved.
