-
## **Desired feature/enhancement**
Remove all the restraints-related CLIs from the codebase
## **Motivation**
The current implementations of restraint generation routines are a port o…
-
### 📑 I have found these related issues/pull requests
not issue but idea
### 🏷️ Feature Request Type
Dashboard, Settings
### 🔖 Feature description
The functionality would bring a new me…
-
- https://rust-cli-recommendations.sunshowers.io/index.html
- https://clig.dev/#guidelines
- https://smallstep.com/blog/the-poetics-of-cli-command-names/
- https://www.atlassian.com/blog/it-teams/1…
-
### Feature request
I'd like an option to totally ignore all devDependencies and to not recommend moving types to the dependencies array
### Motivations
I might very well be misunderstanding how th…
Tobbe updated
1 month ago
-
Currently, we have two NEAR CLI tools that are causing some issues with developers as both use `near` as a command. This causes conflicts if devs try to use both.
-
Database CLIs usually allow executing a SQL script with many statements.
I guess this can be used to achieve the same effect by executing commands one by one. We may want to support tha…
-
Currently many of the example crates are working CLIs. I doubt however that anyone will ever actually run these CLIs.
The downside of them being CLIs is that they are over 50% just boilerplate for …
-
-
## Checklist
- [X] New Feature for the Service/Plugin (Vatz)
- [ ] Enhancement (Vatz)
- [ ] others(etc. e.g, documentation, project policy management)
---
### **Is your feature request relat…
-
The current CLIs has multiple levels of depth for commands and subcommands, which can be confusing for users IMO.
I propose limiting the depth of commands and subcommands.
For example, we could sw…