Extensions for AEM and IMS do not follow the proper hierarchy in the repo
Open
- Dominant language
- JavaScript
- Stars
- 266
- Forks
- 380
- Avg merge
- 5d 8h
- Merged PRs (30d)
- 9
Description
## What are the schemas that are affected by the issue
\extensions\IMS
\extensions\AEM
## What are examples of products that are impacted by the issue
Not sure.
These schemas should be under a \extensions\adobe\shared\IMS and \extensions\adobe\experience\AEM or simular hierarchy.
Contributor guide
Research direction
Start by reviewing the schemas in extensions/IMS and extensions/AEM and compare their locations with the proposed extensions/adobe/shared/IMS and extensions/adobe/experience/AEM hierarchy. Done means the affected schemas follow the agreed hierarchy without breaking their repository organization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100