mirror of
https://github.com/SillyTavern/SillyTavern-Docs.git
synced 2026-10-16 21:42:51 +00:00
[PR #70] [MERGED] Update example manifest.json #76
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
SillyTavern/SillyTavern-Docs#76
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/SillyTavern/SillyTavern-Docs/pull/70
Author: @johnbenac
Created: 4/9/2024
Status: ✅ Merged
Merged: 4/9/2024
Merged by: @Cohee1207
Base:
main← Head:patch-1📝 Commits (2)
d2ea1beUpdate manifest JSON Docsc5f68d6Update Writing-Extensions.md📊 Changes
1 file changed (+15 additions, -8 deletions)
View changed files
📝
For Contributors/Writing-Extensions.md(+15 -8)📄 Description
Removed inline comments from the manifest.json example provided in the documentation.
Updated the documentation to separately explain each field of the manifest.json file, ensuring clarity for users who may copy the example directly.
Reason for Changes:
The original manifest.json example included inline comments to describe each field's purpose and requirements. However, JSON does not support comments, and users copying the example directly into their projects might encounter parsing errors if they do not realize that these comments need to be removed. This update aims to prevent such confusion by providing explanations outside of the example JSON structure, ensuring that both novice and experienced developers can successfully utilize the example with minimal modifications and less mistakes.
This update ensures our documentation is both accurate and user-friendly, reducing the risk of errors for developers integrating their extensions.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.