Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

beet don't include all files #419

Open
edayot opened this issue Aug 15, 2023 · 1 comment
Open

beet don't include all files #419

edayot opened this issue Aug 15, 2023 · 1 comment

Comments

@edayot
Copy link
Contributor

edayot commented Aug 15, 2023

files named [".mcfunction","..mcfunction","...mcfunction"] are not copied during beet build

In vanilla it's possible to reference such function, and make loading existing datapack not build with beet not working at all.

Here's an example :

erwan@erwan-pc-portable-ubuntu:~/Documents/Dev/beet/examples/code_void$ cat beet.yaml 
data_pack:
  load: [.]
resource_pack:
  load: [.]

output: build


pipeline:
  - add_header
erwan@erwan-pc-portable-ubuntu:~/Documents/Dev/beet/examples/code_void$ cat add_header.py 


from beet import Context, Function



def beet_default(ctx: Context):
    for f in ctx.data.functions.keys():
        ctx.data.functions[f]=Function(f"say {f}")

erwan@erwan-pc-portable-ubuntu:~/Documents/Dev/beet/examples/code_void$ tree -la
.
├── add_header.py
├── beet.yaml
├── build
│   └── code_void_data_pack
│       ├── data
│       │   └── test
│       │       └── functions
│       │           ├── a
│       │           │   ├── a.mcfunction
│       │           │   ├── a.py.git.mcfunction
│       │           │   └── .mcfunction.mcfunction
│       │           ├── a.mcfunction
│       │           ├── a.py.git.mcfunction
│       │           ├── .mcfunction.mcfunction
│       │           └── .mcfunction.mcfunction.mcfunction
│       └── pack.mcmeta
└── data
    └── test
        └── functions
            ├── a
            │   ├── a.mcfunction
            │   ├── a.py.git.mcfunction
            │   ├── ...mcfunction
            │   ├── ..mcfunction
            │   ├── .mcfunction
            │   └── .mcfunction.mcfunction
            ├── a.mcfunction
            ├── a.py.git.mcfunction
            ├── ...mcfunction
            ├── ..mcfunction
            ├── .mcfunction
            ├── .mcfunction.mcfunction
            └── .mcfunction.mcfunction.mcfunction

10 directories, 23 files
erwan@erwan-pc-portable-ubuntu:~/Documents/Dev/beet/examples/code_void$ 
edayot added a commit to edayot/beet that referenced this issue Apr 4, 2024
@edayot
Copy link
Contributor Author

edayot commented Apr 4, 2024

In the fork that I created here in the build directory there is now all the files.

But I don't know if it's the way to do it.

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

No branches or pull requests

1 participant