amplication / amplication/amplication

🐛 Bug Report: Project Configuration Base Directory not applied to Child Services

Open
#3,645 1 comment 0 reactions 0 assignees View on GitHub
type: bug
Dominant language
TypeScript
Stars
16k
Forks
1.5k
PR merge metrics
No merged PRs in 30d

Description

### What happened?

The Base Directory set in the Workspace Project Configuration Settings seems to be ignored by child services.

### What you expected to happen

My expectation is that if I set the base directory to `/apps` in the root Project Configuration Settings, any child app will be generated under this path. Instead, it's generated at the repo's root.

This can interfere with users who want to graudally adopt Amplication into an existing monorepo.

### How to reproduce

1. Create a new Workspace
2. Go to the Project Configuration Settings, set base directory to `/something`
3. Create a new Service
4. Commit & Build

The service is generated at the repo's root, instead of inheriting the base path set by the Project Configuration Settings.

### Amplication version

0.15.2

### Environment

_No response_

### Are you willing to submit PR?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.