@nxlv/python
Advanced tools
Comparing version 18.1.0 to 18.2.0
@@ -0,1 +1,7 @@ | ||
# [18.1.0](https://github.com/lucasvieirasilva/nx-plugins/compare/nx-python-v18.0.1...nx-python-v18.1.0) (2024-05-14) | ||
### Features | ||
- **nx-python:** add support for poetry-plugin-export@1.8.0 ([#207](https://github.com/lucasvieirasilva/nx-plugins/issues/207)) ([28d4ae3](https://github.com/lucasvieirasilva/nx-plugins/commit/28d4ae3c456f75d95d1684aa3dee505b482a7f04)), closes [#206](https://github.com/lucasvieirasilva/nx-plugins/issues/206) | ||
## [18.0.1](https://github.com/lucasvieirasilva/nx-plugins/compare/nx-python-v18.0.0...nx-python-v18.0.1) (2024-03-27) | ||
@@ -2,0 +8,0 @@ |
@@ -9,2 +9,7 @@ { | ||
}, | ||
"publish": { | ||
"implementation": "./src/executors/publish/executor", | ||
"schema": "./src/executors/publish/schema.json", | ||
"description": "publish executor" | ||
}, | ||
"add": { | ||
@@ -11,0 +16,0 @@ "implementation": "./src/executors/add/executor", |
{ | ||
"name": "@nxlv/python", | ||
"description": "Custom NX Plugin to support the Python language", | ||
"version": "18.1.0", | ||
"version": "18.2.0", | ||
"main": "./src/index.js", | ||
@@ -6,0 +6,0 @@ "generators": "./generators.json", |
@@ -515,2 +515,18 @@ # @nxlv/python | ||
#### publish | ||
The `@nxlv/python:publish` executor handles the `poetry publish` command for a project. | ||
#### Options | ||
| Option | Type | Description | Required | Default | | ||
| --------------- | :-------: | ----------------------------------------------------------------------------------- | -------- | ------- | | ||
| `--silent` | `boolean` | Hide output text | `false` | `false` | | ||
| `--buildTarget` | `string` | Build Nx target (it needs to a target that uses the `@nxlv/python:build` execution) | `false` | `build` | | ||
This executor first executes the `build` target to generate the tar/whl files and uses the `--keepBuildFolder` flag to keep the build folder after the build process. | ||
For must scenarios, running the `poetry publish` with `@nxlv/python:run-commands` executor is enough, | ||
however, when the project has local dependencies and the `--bundleLocalDependencies=false` option is used, the default `poetry publish` command doesn't work properly, because the `poetry publish` command uses the current `pyproject.toml` file, which doesn't have the local dependencies resolved, the `@nxlv/python:publish` executor solves this issue by running the `poetry publish` command inside the temporary build folder generated by the `@nxlv/python:build` executor, so, the `pyproject.toml` file has all the dependencies resolved. | ||
#### run-commands (same as `nx:run-commands`) | ||
@@ -517,0 +533,0 @@ |
import { ExecutorContext } from '@nx/devkit'; | ||
import { BuildExecutorSchema } from './schema'; | ||
export default function executor(options: BuildExecutorSchema, context: ExecutorContext): Promise<{ | ||
success: boolean; | ||
}>; | ||
import { BuildExecutorOutput, BuildExecutorSchema } from './schema'; | ||
export default function executor(options: BuildExecutorSchema, context: ExecutorContext): Promise<BuildExecutorOutput>; |
@@ -69,2 +69,3 @@ "use strict"; | ||
return { | ||
buildFolderPath, | ||
success: true, | ||
@@ -76,2 +77,3 @@ }; | ||
return { | ||
buildFolderPath: '', | ||
success: false, | ||
@@ -78,0 +80,0 @@ }; |
@@ -13,1 +13,6 @@ export interface BuildExecutorSchema { | ||
} | ||
export interface BuildExecutorOutput { | ||
buildFolderPath: string; | ||
success: boolean; | ||
} |
import { ExecutorContext } from '@nx/devkit'; | ||
import { ToxExecutorSchema } from './schema'; | ||
export default function executor(options: ToxExecutorSchema, context: ExecutorContext): Promise<{ | ||
export default function executor(options: ToxExecutorSchema, context: ExecutorContext): Promise<import("../build/schema").BuildExecutorOutput | { | ||
success: boolean; | ||
}>; |
Sorry, the diff of this file is not supported yet
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
355269
144
2984
551
21