RFC: Additional KV Data to Links

[ChakshuGautam]

Is your feature request related to a problem? Please describe.
Add any of your own key-value parameters to a yaus link.

[Pankajjsuthar]

Can we say it as branded URLs like generally we use bitly as url shortener so their url look like bit.ly/_home_page/ but we want to look like personal_brand_name/home_page/_shortened_url

If I am thinking right then it would be an interesting problem to solve. Assign me this and I got a question that does it have a deadline of 10th June....

[Nazi-pikachu]

Hey @ChakshuGautam
For implementing the KV data feature. I and @yuvrajsab have been discussing these two possible implementation.
Can you please give your suggestions on this , it would be helpful to get a sense of what would be a better way to do this.

1. Dynamically passon : In this way of implemting we are not storing the KV data in DB instead the liberty is with the user to pass any query params in the shorten link and it will get dynamically added to the long url as well.
2. User specify allowed query params key at the time of registrations and then only allow those fields. (* to allow everything same as a pass on ).
   for ex :-

params: {
allowed : [ "$marketing" , ... ]
}

Also do we need to store the each KV data in the DB ?