adobe / adobe/aem-react-editable-components

Unmapped components silently do nothing

Open
#87 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
68
Forks
35
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
If MapTo is not done between a component and a cqType, the Container component will not render it and no logging will be produced.

**Package version**
1.1.10

**To Reproduce**
Steps to reproduce the behavior:
1. Create some custom component
2. Forget to MapTo between that component and the cqType or make a typo on it
3. Include that component in a container

**Expected behavior**
The component is not rendered and the developer gets some visual clue or a log line about what just happened, allowing the developer to suspect of only one or two probable causes.

**Actual behavior**
The component is not rendered and the developer gets no visual clue nor a log line about what just happened, leaving the developer wondering about a wide variety of possible causes.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue with a custom component that is not mapped with MapTo, then trace how the Container handles the unmapped component. Done means the component remains unrendered but provides a visual clue or log line that helps identify the missing or incorrect mapping.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.