twilio-labs / plugin-alias Goto Github PK

Describe the bug
Command alias for Command Use.js (:use) not working

To Reproduce

1. Install sf cli
2. Run sf alias:setup, add a couple of arguments {wn : whatsnew}
3. Run sf use wn

Expected behavior
Recursively calls the command installed with plugin. Should refer to the 'use' of plugin-alias

Screenshots
Command use when installing

Error Recursive

plugin-alias version: 1.2.0

Additional context
No such issues with Twilio CLI

This repository will inherently lie within the scope of open source. Need for open source-contribution guidelines and template

Is your feature request related to a problem? Please describe.
Test and look out for SonarCloud

Is your feature request related to a problem? Please describe.
Whenever I type Use, or Delete command with a wrong alias_name, I get alias does not exist. I can be given suggestions based on this

Describe the solution you'd like
Match the prefix, or give the options that match my alias_name query

Describe alternatives you've considered
Listing alias again and again and searching for what is required or rather using command itself

Describe the bug
The use(), import() args do not have validateFunctions()
The result is OCLIF error not custom error

To Reproduce
Steps to reproduce the behavior:

1. Go to plugin
2. Run ./bin/run alias:import

Expected behavior
Should return custom error

Setup README.md for usage guidelines

Describe the fix
A few commands have changed. Change the success messages in documentation

Expected behavior
Get updated success messages in documentation

Is your feature request related to a problem? Please describe.
This is not a problem, but as we are releasing a plugin from twilio-labs, other plugins which are already there are using the lowercase style only. Thus it will create a uniformity and ease of use for the user as well.

Describe the solution you'd like
The commands like - "alias:Add" can be changed to "alias:add"

Describe alternatives you've considered
We could have ignore it, but it was pointed out by the help-oss team also, so we should address this one.

Describe the fix
The Licence should have the name as 'Twilio Inc.' While the package.json and readme should have the name as 'twilio-labs'

Expected behavior
These names should be corrected so that we can public the repository

Screenshots
Not Applicable

Desktop (please complete the following information):

• OS: MacOS
• Browser: Chrome
• Version: 103.0.5060.53 (Official Build) (arm64)

Additional context
Not required

Is your feature request related to a problem? Please describe.
If we could add a path for exporting the data file

Describe the solution you'd like
Pass as arguments/flags

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Describe the fix
Make tests more concise

Expected behavior
The tests are too vast

Is your feature request related to a problem? Please describe.
Not a problem per se. But it makes little sense to have two different aliases for same command.

Describe the solution you'd like
Currently, we are accepting the case when user is saving same command with two different aliases. E.g:
plist: profiles:list
prlist: profiles:list

However it makes less sense to have two different aliases for one single command. Can think of having a bidirectional one-to mapping between aliases and commands.

Describe alternatives you've considered
We considered the alternative of using an update command. Maybe that can be taken in next sprint.

Create an issue template for the usage

Describe the bug
The Licence should have the name as 'Twilio Inc.' While the package.json and readme should have the name as 'twilio-labs'

Expected behavior
These names should be corrected so that we can public the repository

Is your feature request related to a problem? Please describe.
Use external library commitizen for PR and commit titles

Additional context
Needed for semantic release

Describe the need and headers of the documentation
Require the README.md to contain updated commands

Is your need for documentation related to a problem? Please describe.
The behaviour listed in README.md is different from the actual behaviour (success messages, features)

Additional context