Summary:

• Changelog matching using regex as in .github/chglog/release.yml, currently matched for current type feat: something, can also process feat(subtopic): something as well, subtopic will appear bold if present in the changelogs.
• Release template based on simple markdown file completely flexible, present at .github/chglog/RELEASE.tpl.md
• Added workflow that builds on variety of platforms as here .github/workflows/release.yml

Sample tested action Release output

^ made using the following cmds

git tag v0.0.9
git push origin v0.0.9

Notes: made it failsafe so should release those builds where atleast one of platform is able to build, and build fails should be available at actions section to monitor any.

Make a UI design for the TUI in a design software like Figma, Adobe Xd, or Sketch.

We're looking for a design where we can accommodate a search bar, a list view of the available templates, and a preview of the boilerplate repository if possible. Any further additions are welcome.

Give a link to your design file in the README while making the PR, and make sure the link that you give is made public. (You may also include screenshots of the design in the PR if you wish)

Few changes were made in the PR #32 and subsequently TUI was also changed. The new GIF will be implemented in #49. Please make the required changes in the README which shows how to use the Live Search.

The task is to record a neat GIF showing all features and usage of the application and put it in the README and to remove the old one. Show the features accomplished in #42.

Implement a progress bar or a pre-loader predominantly to be used when the repository is being cloned. But make sure to make it an independent and modular function so that other functions can call it in case it is needed.

We're planning on releasing a new website for Templa-rs which will contain the links to all the releases packages, and basic usage guidelines for the project.

It should be an aesthetic single paged website that will contain all that's said above. The design can be made in any design software and the link can be added to the README for the PR.

Describe the bug

Currently, templa-rs uses submodules.json file to load and display the available templates, but while creating a release, this is not included, hence it isn't ready to ship solution yet.

To Reproduce Steps to reproduce the behaviour:

1. Build templa-rs using cargo build
2. Place the binary in a directory where there isn't any submodules.json

Expected behaviour It should at least have a minimal amount of repos already pre-built for user to select

Screenshots

Desktop (please complete the following information):

• OS: Linux/Windows

Proposed Solution(s)

1. Refer to the submodules.json file from GitHub while running the command
2. Create a small key/value storage and store the data (serialize and deserialize on startup)

On every PR to master branch, scan for vulnerabilities. The choice for method to be used lies with the contributor! Fail the CI if any vulnerability is found (even if not severe).

I created a new App struct to store the app's current state in. This makes the code a little bit cleaner, as it separates the app's state from the drawing logic. With this change, the search feature has been optimized: now it caches the results in the app struct, and it performs new searches if and only if it needs to (For now, it searches only once, but this will become more relevant once we add a search bar). Also, by doing this i fixed the fact that on empty searches nothing was shown (now it shows every possible template), and the broken wrap around when a user tries to go up at index zero in the list, or down at the last index (previously, the cursor would disappear, and the program would crash if you pressed Enter).

All these changes will help to create further menus more easily, as now you can potentially track what menu you're in directly inside the app status.

Re: #52

Was this what you guys were hoping for? Obviously haven't added the GIF yet but other than that what do you think? Any changes let me know and I'll be happy to make them - or if its completely not what you wanted I can give it another shot

NB: See #49 for my question regarding the GIF

Currently, new threads are created while scraping every repository. In order to increase efficiency, use the crate ThreadPool to manage the threads. This was discussed in #42 .

You'll have to make a static website that explains the objective of the project and provides links to packages for all platforms. A SPA (Single Page Application) should be enough. This will depend on #53.

As mentioned in #3, you'll need to implement the repository URL, stars and forks along with the repository name. (Issues are optional). The Figma board for the design can be found here.

Improve the searching algorithm present in perform_search().

Currently, the search works in an O(n) time complexity by comparing the input given by the -t flag with the tags array in the submodules.json.

In the submodules.json file add new template repositories for different languages and architectures in the following format -

{
        "name" : "<repo_name>",
        "url" : "<repo_url>",
        "tags" : ["<tags_relevant_to_repo>","<>","..."]
}

Please don't reference this Issue whilst opening a PR, as this issue will be indefinitely opened to encourage addition of more templates.