How to use the `ignoreFiles` option?

[tukusejssirs]

I have just found your Nx plugins and it looks promising!

However, I want to ignore some files from being copied during the build step.

In options.ts, I have found the ignoreFiles option:

nx-php/packages/phpbuild-executor/src/options.ts

Lines 1 to 5 in 3c0e648

	export interface PhpBuildOptions {
	outputName: string | null;
	outputPath: string | null;
	ignoreFiles: string[] | null;
	}

I have apps/app/dockerfile, however it is copied to {options.outputPath}/{options.outputName}, whether I set ignoreFiles to ["dockerfile"] or ["apps/frontend-php/dockerfile"].

Anyway, here is my apps/app/project.json:

apps/app/project.json

{
  "$schema": "../../node_modules/nx/schemas/project-schema.json",
  "name": "app",
  "projectType": "application",
  "sourceRoot": "apps/app/src",
  "tags": [],
  "targets": {
    "build": {
      "dependsOn": [
        "copyComposerJson"
      ],
      "executor": "@nx-php/phpbuild:phpbuild",
      "options": {
        "ignoreFiles": [
          "apps/app/dockerfile"
        ],
        "outputName": "app",
        "outputPath": "dist/apps"
      },
      "outputs": [
        "{options.outputPath}/{options.outputName}"
      ]
    },
    "copyComposerJson": {
      "executor": "nx:run-commands",
      "options": {
        // Note: This script copies the Composer files to `dist/apps/app`
        //       so that I could create a Docker image from the files in `dist/apps/app` only.
        "command": "node scripts/copy-file.js composer.json composer.lock dist/apps/app"
      }
    },
    "test": {
      "dependsOn": [
        "build"
      ],
      "executor": "@nx-php/phpunit:phpunit"
    }
  }
}

Thanks for the creation of these plugins! 🙏

Versions:

• @nx-php/composer-plugin@0.2.0;
• @nx-php/phpbuild@0.1.2;
• @nx-php/phpunit@0.2.0;
• nx@19.2.3.

[damienwebdev]

@tukusejssirs unfortunately, this flag is currently supported. We originally had this flag at the outset of the project, but we realized that we would never be able to meet compatibility with what would come off of Packagist if you were to try to install your package that way (like a user would).

If you wanted to approach this issue from the scope of a PR/change to the composer executor, the correct change is to modify the executor to perform an archive first and then, unzip those files as output to {options.outputPath}/{options.outputName}.

I haven't had the time to implement this, but it wouldn't be too hard to do.

This would ensure that whatever you build for yourself locally winds up the same as what would wind up on Packagist.

If you're willing to give this a stab, I'd gladly accept a PR.