go: `//go:embed ` doesn't work

I agree. It makes sense to limit go:embed access to the whole directory of the current module rather than the current directory. One should be able to embed files within the whole “sub-tree” of the root directory of the current module. Right now, I end up applying the following pattern:

//go:generate cp -r ../../assets ./local-asset-dir
//go:embed local-asset-dir
var assetFs embed.FS

This works but it looks bad and I would like to avoid it.

Wouldn’t it be nice if embed could support predefined variables like ‘dirname’ or ‘projectname’ to avoid some unexpected bug and thus avoid the ‘…’ or ‘.’?

This is intentional and documnted

Patterns may not contain ‘.’ or ‘…’ or empty path elements, nor may they begin or end with a slash.

This was an explicit design decision:

Because embed.Files implements fs.FS, it cannot provide access to files with names beginning with …, so files in parent directories are also disallowed entirely, even when the parent directory named by … does happen to be in the same module.

ref: https://go.googlesource.com/proposal/+/master/design/draft-embed.md

maybe do this，Create a new assets.go in the directory that needs to be packaged

package assets

import "embed"

//go:embed *
var Assets embed.FS

Then use this variable in another package

a :=&assets.Assets

it sounds nice! Maybe we should make a new issue @JuanigTorres ?

If it’s still relevant I found good answer here.

it sounds nice! Maybe we should make a new issue @JuanigTorres ?

yah, this solution is possible, but it would be a bit crazy. I’d need to add go:embed directive in main.go and pass on embeded variable to my app? it doesn’t seem right.

It still can’t cross module boundaries, and if it’s in the same module you can just put the embed directive in a go file in the parent directory

It is stupid to just match child direction. Why do you always want to teach us how to layout our projects?

@korya , does your solution work to embed one file into a slice of bytes?

It should work.

@korya what do you mean by go:generate ../../assets ./local-asset-dir?

Sorry, there is a typo. I missed cp -r. It should be //go:generate cp -r ../../assets ./local-asset-dir. I’ve fixed my original post.