-
-
Notifications
You must be signed in to change notification settings - Fork 132
[Feature] - Migrating to a new snippet storage system #87
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
Comments
View the implementation in #88 |
@psychlone77 @saminjay |
This feature has been implemented. #88 |
Please do not close it for the moment, it serves as an information that we changed the storage system |
As everything went pretty well with the migration, and pull requests are updating to the new way of adding snippets, i will close this issue |
Uh oh!
There was an error while loading. Please reload this page.
What feature would you like to see?
Hi everyone!
After some discussions with our contributors and maintainers, we’ve decided to move to a new snippet storage system to keep up with our growing collection of snippets.
The Problem
Our current setup of storing snippets in a JSON file is starting to cause a few problems:
Our proposed solution
We’re planning to switch to a Markdown-based system. Here’s what the new structure would look like:
language
andcategory
will be folders and each snippet will be in its own Markdown file.Here’s the snippet format:
New Field:
contributors
There's planned to be a new field, called
contributors
. This field is for recognizing anyone who improves or refines a snippet in the future. The original author will still get credit, but contributors will also be listed so everyone gets the recognition they deserve.Read more in CONTRIBUTING.md file.
Thoughts
We believe that this system will be easier for both parties, contributors and maintainers to add, edit and review snippets.
We’d love to hear your feedback on this plan! If you’ve got suggestions or ideas, feel free to share them here. We’ll keep this issue updated as we work through the migration. 🚀
Thanks for being part of this journey and helping improve QuickSnip!
Generated by ChatGPTThe text was updated successfully, but these errors were encountered: