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).

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.

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)

Design an ASCII Art Logo with the name "Templa-rs".

Add it to the TUI preferably as a block as well as in the help command output.

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)

Describe the bug
The bug is caused since The arch package libgit2 is flagged out-of-date: https://archlinux.org/packages/extra/x86_64/libgit2/. Reference1 Reference2

To Reproduce
Steps to reproduce the behavior:

1. Go to templa-rs directory and try to execute the commands
   cargo run -- -t react -n "check"
2. Select any of the templates and hit enter
3. You will see the error invalid version 0 on git_proxy_options; class=Invalid (3) ] 0/100

Expected behavior
Clone any selected template

Screenshots

Desktop:

• OS: Manjaro KDE ArchLinux systems

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.

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.

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.

For now the search parameter is being taken as a flag (-t/--type), instead implement a input box in TUI and return matching results on every keypress. A reference for the same can be found here.

The preview of the repository can be shown while the user browses through the available templates on another block aside the search results.

The available files and folders in the repository shown as a tree would suffice.

You can either scrape the repository or recursively clone the repositories. Any better method is welcome!

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.

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 .

Describe the bug
If the user does not give a name for template then they will see the error:cannot pick working directory for non-bare repository that isn't a '.git' directory; class=Repository (6)

To Reproduce
Steps to reproduce the behavior:

1. Go to templa-rs directory and try to execute the command
   cargo run --
2. Select any of the templates and hit enter
3. You will see the error cannot pick working directory for non-bare repository that isn't a '.git' directory; class=Repository (6)

Expected behavior
The name of the boilerplate-template should be used instead of the error

Screenshots

Currently, the submodules.json is static with the version of the compiled binary. If any changes in the submodules.json is made in the repo, the updated results aren't shown to the users.

To solve this, fetch the submodules.json from the repository and display live results.

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.

Describe the bug
Error messages are not unwrapped

To Reproduce
Steps to reproduce the behavior:

1. Clone a repo using templa-rs
2. re-clone using the same name
3. You will find the error "Error Encountered while cloning, Ok("fatal: destination path 'new_proj' already exists and is not an empty directory.\n")"

Expected behavior
Error should be unwrapped into stderr like:

fatal: destination path 'new_proj' already exists and is not an empty directory.

Screenshots

Desktop (please complete the following information):

• OS: All Platforms

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.

Create a CI to release binaries for UNIX based systems as well as Windows and automatically create changelogs.