Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement #1 #2

Conversation

Pandademic
Copy link
Owner

This will be merged once fully stable

@Pandademic Pandademic added the critical critical issue label May 26, 2022
@Pandademic Pandademic added this to the 0.1 milestone May 26, 2022
@Pandademic Pandademic linked an issue May 26, 2022 that may be closed by this pull request
Pandademic added 2 commits May 27, 2022 11:08
How?
by having args as a slice that the CLI can acess , so an unlimetd number
of arguments can be passed.[WIP]
By stable I mean ready to merge.

What was the minor bug , you may ask?

Function shiftArgsDownward returns the slice , and does not modify it.

Previously Args was not set to shiftArgsDownward(Args) , so it stayed
unmodified

Yes , future me I ran go fmt
@Pandademic
Copy link
Owner Author

This is can now be merged once the docs are adjusted to this

@Pandademic
Copy link
Owner Author

Were good to go!

@Pandademic Pandademic merged commit 2ccc8e1 into main May 27, 2022
@Pandademic Pandademic deleted the issue-1-_ESSENTIAL_Set_a_variable_to_tell_what_arguments_were_passed branch May 27, 2022 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
critical critical issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[ESSENTIAL] Set a variable to tell what arguments were passed
1 participant