CLI Feature: Hot commands

srinjoyc commented 3 years ago

👋 If you are interested in working on this issue, please check out the Getting Started guide on HackerEarth!

Description (Problem Statement)

The flow CLI should be customized to provide easy access to common commands. The structure of the commands help screen is depicted in Figure 1. Initially deploy, run and init commands should have aliases.

Usage:
  flow [command]

Hot Commands:
  init       Initialize configuration
  deploy     Deploy contracts
  run        Start emulator and deploy contracts

Available Commands:
  accounts     Utilities to manage accounts
  blocks       Utilities to read blocks
  cadence      Execute Cadence code
  collections  Utilities to read collections
  emulator     Starts the Flow emulator server
  events       Utilities to read events
  help         Help about any command
  keys         Utilities to manage keys
  project      Manage your Cadence project
  scripts      Utilities to execute scripts
  transactions Utilities to send transactions
  version      View version and commit information
  config       Configuration commands

Figure 1. Command structure

Experience Required

Experience with Go

Minimum Feature Set (Acceptance Criteria)

Customize help screen to have "hot commands" section that includes all commands that have existing aliases
Implement command aliases without duplicating the command code

Milestone Requirements

Meet minimum feature set

Software Requirements

Maintainability

Code should be written with best practices in mind.

Testing

Tests should cover all the code implementing this functionality.

Other Requirements

Documentation

Documentation should be updated according to the changes made.

Code standards or guidelines

Follow the general contribution guidelines.

Judging Criteria

For all projects, technical & high-level judging criteria apply.

Resources

sideninja commented 3 years ago

Hi 👋 my name is Gregor, and as a software engineer working on developer tools, I will be your point of contact for this task, so good luck, and don't hesitate to reach out to me with any problems or questions.

I'll keep an eye on your progress and will be reviewing your code.

You can comment here or find me on Discord (I'm sideninja#1970). Join the Flow Discord server if you're not there already!

monalisha31 commented 3 years ago

Hello,

I would like to work on this issue. I will be working solo. Following are the required details.

Team Name- monalisha31
Team Link- https://www.hackerearth.com/challenges/hackathon/flip-fest/dashboard/db9ee23/team/
Team member- @monalisha31
Deadline for first milestone- about 2 weeks

eburnette commented 3 years ago

Do you think the best approach is to add the feature to the cobra CLI library?

sideninja commented 3 years ago

Do you think the best approach is to add the feature to the cobra CLI library?

Cobra has a way to modify and create templates, so that is probably a good way to start.

mujtaba1747 commented 3 years ago

Hi @sideninja We want to work on this issue Team: https://www.hackerearth.com/challenges/hackathon/flip-fest/dashboard/27ca50a/team/view/ Members: @mujtaba1747 @vedantatrivedi @jinit24 Deadline: 2 weeks

We are open to working together with other team/induviduals as well

psiemens commented 2 years ago

Hey @mujtaba1747, that's great!

For tier 3 tasks, you can get started right away.

sakshamb2113 commented 2 years ago

Hi, can I work on this ? Team- https://www.hackerearth.com/challenges/hackathon/flip-fest/dashboard/1499406/team/ Member- @sakshamb2113

sideninja commented 2 years ago

Hi, can I work on this ? Team- https://www.hackerearth.com/challenges/hackathon/flip-fest/dashboard/1499406/team/ Member- @sakshamb2113

For sure you can :) but be careful about the deadline 1. Nov.

kimcodeashian commented 2 years ago

Good day @sakshamb2113!

Thanks so much for all your hardwork & participation. In order to finalize winners & prepare for prize payout, we'll need the following actions from your end.

Please provide the following information by Nov 17, 2021, (in this GH Issue is fine):

1. Team Information

Team Members Information - Github Username + Email Contact + Percentage of prize allocation (total should = 100%)
All mentioned members MUST react to the post with a 👍 which will act as confirmation that the information is correct, or a 👎 to indicate that the information is not correct.
We will be reaching out via e-mail

🎖IMPORTANT: We will only proceed with prize payouts once all members have confirmed with 👍 on the post.

2. Video Demo (optional)

Please provide a 5-minute video demo to be featured & showcased in the FLIP Fest Closing Ceremonies
Link format & Downloadable (eg. Google Drive, Vimeo)
Content Format (Problem Statement, your work / how you solved it, final outcome)

We will be hosting Closing Ceremonies on November 23rd, 8AM PT where we'll having closing remarks from Dete & will be announcing the winners! I'll share the details here before Nov 17.

sakshamb2113 commented 2 years ago

Hi @kimcodeashian ! Please find the team details

Team Members-

@sakshamb2113 sakshamb2113@gmail.com 100%

kimcodeashian commented 2 years ago

Hey folks,

We've received and reviewed over 82 submissions! What an amazing community on Flow! To commemorate all the hard work done, we have finalized winners and will be announcing them during our Closing Ceremony on Nov 23rd, 8AM PT. Be sure to join us - there may be some attendance prizes & a keynote from our CTO, Dete 😉!

RSVP here so you don't miss out! See you then!

onflow / flip-fest