Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

bhansa
bhansa
Offline

Badges

Badges
17

Accepted Solutions

Accepted Solutions
1

Likes Received

Likes Received
7

Posts

Posts
15

Discussions

Discussions
3

Questions

Questions
12

Ideas

Ideas
0

Blog Posts

Blog Posts
2
Top badges earned by bhansa
Customize the badges you want to showcase on your profile
Re: [AEM GEMs] Build Sites Faster with AEM Headless and App Builder - Adobe Experience Manager 01-04-2022
Very good session, to the point. @duypnguyen 

Views

3.5K

Likes

2
Re: [New] Welcome to AEM Community! Please Introduce Yourself - Adobe Experience Manager 01-04-2022
Hi Everyone, I am Bharat Saraswat, a Senior Frontend Developer at Deloitte. I have been working on AEM for 5 years now, during these five years I have got a good grasp of AEM development lifecycle, configuration, workflows. I am best known for working with Client Libraries and integrating complex frontend frameworks with AEM. I have been also working as a community manager and facilitator outside my work, very excited to be part of this community. 😊🤝 You can talk to me about: Maven; AEM; React...

Views

149

Like

1
Updating OSGi configuration for running AEM cloud instance - Adobe Experience Manager 01-04-2022
Hi, Hope everybody is doing well. I wanted to know if we have a way to update OSGi configs such as HTML Library manger via some API. Why API? Since in ACS we do no have access to /system/console and cannot update the immutable data(please correct if I am wrong). I would like to know a way of updating these configurations without any builds. Thanks,Bharat Saraswat

Views

114

Likes

0

Replies

1
Re: AEM Cloud manger build failing due to large build log size - Adobe Experience Manager 01-04-2022
Finally, this setting is working fine: "htmllibmanager.processor.js": [ "default:gcc;languageIn=ECMASCRIPT_2019;languageOut=ECMASCRIPT_2015;compilationLevel=whitespace", "min:gcc;languageIn=ECMASCRIPT_2019;languageOut=ECMASCRIPT_2015;compilationLevel=whitespace" ],It gets rid of the above $jscomp error as well the strict type checking, if using ECMASCRIPT_2015 language in parameter.

Views

93

Like

1

Replies

0
Re: How can we disable strict mode while running min:gcc - Adobe Experience Manager 31-03-2022
Can you tell what's the correct format please for AEM.

Views

117

Likes

0

Replies

0
Re: AEM Cloud manger build failing due to large build log size - Adobe Experience Manager 30-03-2022
Thanks for the reply @anish-s This jscomp variable is coming from the gcc compiler scripts I believe.Whenever languageIn=ECMASCRIPT_2015; is used, it adds some extra code in clientlibs, and that's why this error. l.r = function(e) { $jscomp.initSymbol(); $jscomp.initSymbol(); $jscomp.initSymbol(); "undefined" != typeof Symbol && Symbol.toStringTag && Object.defineProperty(e, Symbol.toStringTag, { value: "Module" }), Object.defineProperty(e, "__esModule", { value: !0 }) }

Views

111

Like

1

Replies

1
Re: AEM Cloud manger build failing due to large build log size - Adobe Experience Manager 29-03-2022
So, here is the update I have which seems to be working. I have update the osgi config for HTML library manager to: "default:gcc;languageIn=ECMASCRIPT_2015;compilationLevel=whitespace", "min:gcc;languageIn=ECMASCRIPT_2015;compilationLevel=whitespace" This is working but now the pages are throwing error in console: `Uncaught ReferenceError: $jscomp is not defined`

Views

119

Like

1

Replies

3
AEM Cloud manger build failing due to large build log size - Adobe Experience Manager 29-03-2022
Hi, The AEM cloud manager build is failing due to the large size of build log file > 500MB.The errors are mostly related to JS syntax, for example:ERROR - This language feature is only supported for ECMASCRIPT6 mode or better: arrow function. const toType = obj => { Let me know if any solutions for this, how to get rid of these errors during build.Note: The UI and functionality is working fine, these errors are there during build. Thanks,Bharat

Views

150

Likes

0

Replies

6
Coral ids and attributes are getting added after the Coral.commons.ready - Adobe Experience Manager 10-03-2022
Hi, I have a situation where my code is relying on some of the ids and attributes which are getting added on the Coral component.The Moment when Coral.commons.ready is triggerred the DOM looks like this: After I remove my breakpoint from code, I see other attributes getting added: Since they are getting added later my code is not able to capture those. This was not the case with previous touch UI dialogs. Thanks,Bharat

Views

116

Likes

0

Replies

0
Re: AEM 6.1 and React Integration - Adobe Experience Manager 02-03-2022
Hi @samr99530769 in case you have done the above integration already, I would like to know the details, challenges which faced and the approach which you followed. Please share. I have a similar use case where I have to built the frontend on a AEM application, my application is very less dependent on AEM authoring and only depends on few of the configuration.

Views

103

Likes

0

Replies

0
Likes from