Plugins that contain controllers don't compile yet
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.6k
- Forks
- 175
- PR merge metrics
- No merged PRs in 30d
Description
Given the following plugin with the module path `plugin.com`
```
bud-admin/
controller/
admin/
admin.go
plugin.go
go.mod
```
And an application with the following module path `app.com`, if you run `bud build`, you'll get the following:
```
error: mod: unable to resolve directory for package path "app.com/controller/admin": stat
controller/admin: no such file or directory
```
While bud has successfully bundled the admin controller from `plugin.com` into `app.com`, it's messed up the import paths:
- Actual: `app.com/controller/admin`
- Expected: `plugin.com/controller/admin`
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the plugin and application module layouts shown, then run `bud build` and inspect the plugin bundling and import-path resolution flow. The fix is complete when the bundled controller retains `plugin.com/controller/admin` rather than becoming `app.com/controller/admin`, and the build succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100