RFC: Additional KV Data to Links #21

Activity

1. ChakshuGautam

   changed the title [-]Spec for adding Deep Links[/-] [+]RFC: Additional KV Data to Links[/+] on Jun 1, 2022
2. ChakshuGautam

   added

   documentationImprovements or additions to documentationImprovements or additions to documentation

   on Jun 1, 2022
3. ChakshuGautam

   self-assigned this

   on Jun 1, 2022
4. ChakshuGautam

   added

   RFC

   and removed

   documentationImprovements or additions to documentationImprovements or additions to documentation

   on Jun 1, 2022
5. Pankajjsuthar commented on Jun 7, 2022

   

   Pankajjsuthar

   on Jun 7, 2022

   More actions

   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....
6. Nazi-pikachu commented on Aug 29, 2023

   

   Nazi-pikachu

   on Aug 29, 2023

   Collaborator

   More actions

   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 ?