Skip to content

[Plugins] Should the plugin package be moved out of internal? #1688

Description

@linux2647

Version

1.14.0

What happened?

I wanted to play around with authoring a plugin, but after reading the documentation and looking at the example code, I realized that the plugin package, which contains the protobuf-emitted code, lives under internal. By definition this means that no Go code outside of sqlc can import it. I saw that the ultimate goal is to have WASM-based plugins, but #1578 indicates that development on that has been stalled, opting for process-based plugins for the time being.

Am I missing something obvious that makes it possible to write a process-based plugin? Or does the plugin package need to be moved out of internal?

Relevant log output

No response

Database schema

No response

SQL queries

No response

Configuration

No response

Playground URL

No response

What operating system are you using?

No response

What database engines are you using?

No response

What type of code are you generating?

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtriageNew issues that hasn't been reviewed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions