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
BedrockMission!

Learn More

View all

Sign in to view all badges

mrobinson
Community profile mrobinson Level 1
Job title here
Location here
2 BADGES
Level 1

Level 1

Learn more
Joined the community 07-01-2020 5:51:18 AM
Offline
Top badges earned by mrobinson
Customize the badges you want to showcase on your profile
IE11 Does not support es6, and our project will only export es6
Avatar
Validate 1
Level 1
mrobinson
Level 1

Likes

0 likes

Total Posts

11 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Give Back
View profile
mrobinson
- Adobe Experience Manager
Our project’s ui.frontend is rendering our clientlib-site with some ES6 arrow notations. I verified that the arrow notations occur in the dist clientlib-site js file. Not converting ES6 to ES5 causes our site to fail in IE11, which only supports up to ES5. Our tsconfig.json is already set to compile the ui.frontend to ES5 so we are unsure why the compiler is failing to convert everything. tsconfig.json{ "compilerOptions": { "target": "es5", "module": "es6", "baseUrl": "../ui.frontend", "removeCo...

Views

260

Likes

0

Replies

1
Re: AEM Core "Container" components not editable in SPA Editor
Avatar
Validate 1
Level 1
mrobinson
Level 1

Likes

0 likes

Total Posts

11 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Give Back
View profile
mrobinson
- Adobe Experience Manager
I've opened an Adobe support ticket on this since there has not been any significant movement.

Views

188

Likes

0

Replies

0
AEM Core "Container" components not editable in SPA Editor
Avatar
Validate 1
Level 1
mrobinson
Level 1

Likes

0 likes

Total Posts

11 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Give Back
View profile
mrobinson
- Adobe Experience Manager
I've seen several posts/questions around this topic, but never a clear answer. Here is a Git issue that describes it quite well:https://github.com/adobe/aem-core-wcm-components/issues/421 I am currently on AEM 6.5.6 and Core Components 2.11.0 and the issue is still able to be replicated. I attempted to do what was described in the issue: Hi @davidjgonzalez , had a deeper look with @richardhand and @pfauchere from SPA team.The problem is that the carousel dialog expects at least one sub item, in ...

Views

225

Likes

0

Replies

1
Re: SPA App deployment with classic profile
Avatar
Validate 1
Level 1
mrobinson
Level 1

Likes

0 likes

Total Posts

11 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Give Back
View profile
mrobinson
- Adobe Experience Manager
Thank you!!

Views

225

Likes

0

Replies

0
Re: SPA App deployment with classic profile
Avatar
Validate 1
Level 1
mrobinson
Level 1

Likes

0 likes

Total Posts

11 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Give Back
View profile
mrobinson
- Adobe Experience Manager
Understood. Is there anywhere that has the full profile code? In the documentation, it provides some of it, but not all. There is a '...' which I assume contains collapsed code. An additional Maven profile, named classic has been added to modify the build to target AEM 6.x environments: classic false ...

Views

226

Likes

0

Replies

0
SPA App deployment with classic profile
Avatar
Validate 1
Level 1
mrobinson
Level 1

Likes

0 likes

Total Posts

11 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Give Back
View profile
mrobinson
- Adobe Experience Manager
I am trying to deploy an SPA to AEM version 6.5.5 using the -Pclassic build profile, but at the end of the build process, I receive the following warning: [WARNING] The requested profile "classic" could not be activated because it does not exist.Am I missing something in order to include that profile?Thanks!

Views

288

Likes

0

Replies

4
SPA Angular [Title] component mapping
Avatar
Validate 1
Level 1
mrobinson
Level 1

Likes

0 likes

Total Posts

11 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Give Back
View profile
mrobinson
- Adobe Experience Manager
I am attempted to map the Title component in an SPA, but was curious how others were able to map the "type" property to the title.component.html file. title.component.tsimport { Component, Input, OnInit } from '@angular/core'; import {MapTo} from '@adobe/cq-angular-editable-components'; @Component({ selector: 'app-title', templateUrl: './title.component.html', styleUrls: ['./title.component.css'] }) export class TitleComponent implements OnInit { @Input() type: string; @Input() text: string; con...

Views

427

Likes

0

Replies

0
Creating a nested Style Systems navigation
Avatar
Validate 1
Level 1
mrobinson
Level 1

Likes

0 likes

Total Posts

11 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Give Back
View profile
mrobinson
- Adobe Experience Manager
This is more of a feature request type post, but would be curious if there are any thoughts around its feasibility currently. In an effort to reduce the number of components made available to content producers, we're creating style systems that apply the look/feel of the component. In doing so, however, I've noticed that very quickly, the number of options available causes the Style System dropdown to scroll. I've attached screenshots of what I think would be very useful functionality; the abili...

Views

353

Likes

0

Replies

1
Re: Extend AEM Core Carousel Component
Avatar
Validate 1
Level 1
mrobinson
Level 1

Likes

0 likes

Total Posts

11 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Give Back
View profile
mrobinson
- Adobe Experience Manager
Right, but what you can do is select the Adobe Core 'Container' component as the 'Slide' of your carousel. Doing so would allow you to place any number of other components in that 'Slide', such as 3 Image components, and those could be resized using the layout editor of the Container.

Views

1.0K

Likes

0

Replies

0
Re: Extend AEM Core Carousel Component
Avatar
Validate 1
Level 1
mrobinson
Level 1

Likes

0 likes

Total Posts

11 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Give Back
View profile
mrobinson
- Adobe Experience Manager
Just curious, but have you considered having a 'Container' component be the 'Slide', and then you can place 3 Image components within each slides' container? That way you would only have 2 panels, but would still be able to manage/configure the images individually.

Views

1.0K

Likes

0

Replies

4
Re: Experience Fragment - getChildren of null
Avatar
Validate 1
Level 1
mrobinson
Level 1

Likes

0 likes

Total Posts

11 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Give Back
View profile
mrobinson
- Adobe Experience Manager
Yes, you're right. That was the solution we came up with as well.

Views

2.3K

Likes

0

Replies

0