You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+12-4
Original file line number
Diff line number
Diff line change
@@ -1,23 +1,31 @@
1
1
# Voxelite JSON Merger
2
2
3
-
GitHub Action to merge [Voxelite](https://github.com/voxelite)'s `block.json` (main JSON) with all JSONs in `block` directory.
3
+
GitHub Action to merge [Voxelite](https://voxelite.net)'s `block.json` (main JSON) with all JSONs in `block` directory.
4
4
The same can be done for items, entities...
5
5
6
+
This is intended to allow two different approaches of object management (all objects of same type in single file and one file per object) to be used at the same time.
7
+
It also minimizes the JSON by removing unimportant new lines and whitespaces (harder to read for humans but still valid JSON).
8
+
6
9
## Inputs
7
10
8
11
### `in-file`
9
12
10
-
Path to your `block.json` (or equivalent).
13
+
Path to your multi-object file - `block.json` (or equivalent for other object types).
11
14
12
15
This is your main file with data.
13
16
Inside the file you should have a JSON Object with keys for codenames and their values an object with all the configuration.
14
17
18
+
Leave empty when you don't have multi-object file.
19
+
15
20
### `in-directory`
16
21
17
-
Path to your directory containing all object files.
18
-
Inside each object (like a block) is represented by a single JSON file.
22
+
Path to your directory containing all single-object files.
23
+
Inside each JSON file is a single object (like a block or item).
24
+
19
25
Name of the file is used as the object's name and inside is a JSON Object with all the configuration.
20
26
27
+
Leave empty when you don't have directory of single-object files.
0 commit comments