Skip to content

Conversation

bentsherman
Copy link
Member

This PR adds an entrypoint for generating a "plugin index file", which contains a list of plugin definitions (config scopes, functions, etc).

It should be used by the Nextflow Gradle plugin to generate the index file when building/releasing a plugin, and it should be consumed by the plugin registry for use by the language server, registry UI, etc.

Signed-off-by: Ben Sherman <[email protected]>
@bentsherman bentsherman requested a review from pditommaso August 22, 2025 17:47
Copy link

netlify bot commented Aug 22, 2025

Deploy Preview for nextflow-docs-staging canceled.

Name Link
🔨 Latest commit e2cf820
🔍 Latest deploy log https://app.netlify.com/projects/nextflow-docs-staging/deploys/68a8ad48cb6b11000845d2ef

Copy link
Member

@pditommaso pditommaso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does not look to have dependency with the nextflow runtime, does it? could make sense to keep it in its own module or even keep it in the gradle plugin source? it would be preferable to have the gradle plugin to no depend on the main nextflow runtime

@bentsherman
Copy link
Member Author

The PluginIndexWriter does depend pretty heavily on runtime classes, mainly around plugin extensions and config schema. This is why I placed it in a separate configuration, so that the main build doesn't depend on the specific Nextflow version

Long-term, I think we'll want to have a module in Nextflow that defines a versioned "runtime API" that is stable across Nextflow versions. For now I'm just trying to make it work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants