The release build process currently doesn't build the new documentation folder into the release.
Also, the Documentation folders and all markdown files will need Unity .meta files.
Create a Unity Project with Malimbe as an asset, Unity will create the .meta files for commit.
Also, update the package.json in Malimbe to include the Documentation directory
|
"files": [ |
|
"*.md", |
|
"*.meta", |
|
"Editor", |
|
"Runtime" |
|
], |
|
"scripts": { |
|
"prepack": "cp -rf Sources/UnityPackaging/bin/Release/* ." |
|
} |
"files": [
"*.md",
"*.meta",
"Editor",
"Runtime",
"Documentation"
],
Does "Documentation" need to look back in the parent directory? "../Documentation"?
The release build process currently doesn't build the new documentation folder into the release.
Also, the Documentation folders and all markdown files will need Unity .meta files.
Create a Unity Project with Malimbe as an asset, Unity will create the .meta files for commit.
Also, update the package.json in Malimbe to include the Documentation directory
Malimbe/package.json
Lines 25 to 33 in 9cf1ed0
Does
"Documentation"need to look back in the parent directory?"../Documentation"?