Hi @brandonroberts,

I've done some testing and I'm getting some different results than in the description. I think this is due to the fact that this is with the older version then I'm testing right now.

I've done the setup removed the first generated app, and created a second one. This is still similar as you explained.
The first thing I've experienced is that I needed to remove the defaultproject, otherwise I will have the following error:

npx  ng generate @ngrx/schematics:store State --root --module app.module.ts
Project 'first-app' could not be found in the workspace.

The error message is a valid message but I believe this is not the situation you would like to be resolved. After seeing this error message I've removed the defaultProject from the angular.json. This resulted in the following error:

npx  ng generate @ngrx/schematics:store State --root --module app.module.ts
Specified module path /apps/first-app-e2e/src/app/app.module.ts does not exist

The error above is also valid as we have a function in the utility.ts that gets the first project there is from the angular.json file when no default project is provided (or the --project flag).

As I cannot reproduce this issue I just looked at the code and thought of making the following change.

export function getProject(
  host: Tree,
  options: { project?: string | undefined; path?: string | undefined }
): WorkspaceProject {
  const workspace = getWorkspace(host);

  if (!options.project) {
    options.project =
      workspace.defaultProject !== undefined
        ? workspace.defaultProject
        : Object.keys(workspace.projects)[0];
  }

  return workspace.projects[options.project];
}

to:

export function getProject(
  host: Tree,
  options: { project?: string | undefined; path?: string | undefined }
): WorkspaceProject {
  const workspace = getWorkspace(host);

  if (!options.project) {
    if(workspace.defaultProject === undefined){
      throw new SchematicsException(`Could not determine the Angular project. Please provide a '--project' flag.`);
    }
    options.project =
      workspace.defaultProject !== undefined
        ? workspace.defaultProject
        : Object.keys(workspace.projects)[0];
  }

  return workspace.projects[options.project];
}

However, I'm not quite happy with this, because Object.keys(workspace.projects)[0] still could be the one you would like to select by default and with this change, you are forcing people to specifically use the --project file. Could anybody assist me in resolving this issue in the correct way or maybe describe a different approach? I'm also willing to take this offline via twitter or any other medium so that this thread is not filled with many comments.