I am experiencing a challenge while setup my new Angular project with Angular CLI.
I would like to create a folder structure something like below:
-- src
-- components
-- app
-- students
-- faculty
-- admin
-- common
-- search
-- table
-- table_row
-- list
-- list_item
-- header
-- footer
-- side_panel
-- services
-- static
-- jsons
-- cities
-- states
-- time_zones
-- imgs
-- scss
If we run ng g c some-component command it creates new component inside src/app/ only.
In terms of code, app itself is a component, then why does the Angular CLI not allow us to create another component parallel to the app component?
However, it is feasible if we create the folder's structure manually and without using CLI commands. The app also works fine.
Each application has its own size and functionality and needs some specific code design, then why impose such a limitation? Can anyone help me in understanding what the benefit of this structure is?

src/app/feature1..ember-cliblueprints that put everything belowapp, CLI only adds the dir configured asroot.