Feat: Have the ability to add multiple values for the same optional variable

[Darks1de42]

Is your feature request related to a problem? Please describe.
It is not possible to define a variable several times.
For example, applications that make web Requests have the possibility to define Headers.
To do this the flag has to be defined for every header:

-H "Authorization Bearer: <token>" -H "Content-Type: <type>"

Describe the solution you'd like
it would be good if you could specify a variable several times.
And to make that variable and only define these headers when and how often you need that you can define something in your cheat file like that:

curl <header:multiple> example.com

And then in navi you can define the same header multiple times if needed.
This has the advantage, that you don't have to define multiple commands in navi for every flag combination you need.
And it also covers cases that you didn't had in mind during the creation of the command in the cheat file.

This could result for example in one of the following commands:

curl -H "Authorization Bearer: <token>" example.com
curl -H "Content-Type: <type>" example.com
curl -H "Authorization Bearer: <token>" -H "Content-Type: <type>" example.com
curl example.com

Describe alternatives you've considered
It can maybe be solved together with #887

[welcome]

Thanks for opening your first issue here! In case you're facing a bug, please update navi to the latest version first. Maybe the bug is already solved! :)

[alexis-opolka]

Hi @Darks1de42 ,
I struggle to understand the entire logic you're having with this feature request.
Could you give me an example of what you'd like?

A draft would be enough for me to be able to work on it and iterate.

[Darks1de42]

I mean that it would help if you can define special variables multiple times.
For example, some programs accept a flag with an argument multiple times without knowing the exact number this flag is used.
So that you can set for example only one Header -H "Authorization Bearer: <token>" or you set both: -H "Authorization Bearer: <token>" -H "Content-Type: <type>" or even more.

[alexis-opolka]

I understand what you mean now, thank you.

Although this is a good idea I don't know how well it can be used with Navi.

To my knowledge of Navi, there aren't a lot of parameters that would require to be set multiple times in the same command line.

The idea is good but to me there isn't the need to do so.
Maybe some parameters would benefit from this but I would need a specific set.

Making all the parameters callable multiple times wouldn't make any sense.

[Darks1de42]

Hi @alexis-opolka,
I did not mean to have this functionality for navi but for programms defined in the cheat files.
For example I'm using web pentest tools and there you have the oppurtunity to define Web Headers. And sometimes i need them for stuff like Authorization, or sometimes a content Header or Origin Header.
And there could also be cases in other programs where you have to define Flags multiple times.

[alexis-opolka]

Do you mean you can't do what is written below within a cheatsheet?

# Curls a random page while setting two headers
curl -H "Authorization Bearer: <token>" -H "Content-Type: <type>" example.com

[Darks1de42]

I meant to specify it only when it is needed.
So to have curl <header:optional> example.com and if needed add them.
Something like that and when you call the programm with navi you can add them if you want. And as many as you want

[alexis-opolka]

Hmm...

It makes much sense to me now. 😅

That would be pretty useful to put in an optional parameter, that way you wouldn't need to have two different cheatsheets. 🤔
I haven't thought much regarding its implementation but I think it is feasible.

[alexis-opolka]

I took the liberty to modify the title of the issue to better describe your feature request.
Feel free to make modifications.

[Darks1de42]

I took the liberty to modify the title of the issue to better describe your feature request. Feel free to make modifications.

I tried to clarify it a bit in the Issue description

[alexis-opolka]

Thanks. ^-^

[denisidoro]

Out of curiosity: in your use case, what would you type? How would you know when the input finished?

Would you literally type authorization Bearer: 123<enter>content-type:...

If so, I don't see how that would be different from a single var where you can basically type anything