Link (URL) Compatablity

[JeelDobariya38]

As, you have known that we have recently migrate to more microservices like architecture or we can say so... we divide stuff a lot into sub different repository. lik docs website app and so on...

And because of this the url (Link) In app are get deprecated over time... and I think this will continue to go like this.. as my vision for project change often.. So, I want to ask what you think about link compatablity?

• Is it important to you, and i should do something to manage it..
• Or, Should we say that the user will find the things themselves and I should not worry much on this.. It natural thing that url breaks...
• Or I should make smart decision when add url to app, & try avoid break of url.. but this not possible as my vision for project is too vulnerable to changes..

[JeelDobariya38]

Currently, I am try to make link compatablity. By make the old url and new url both vaild.. But I can see that this will become a mess overtime... because handle many url at scale, is not, humanly possible..

So, I am currently find a solution, but there seems to be none.. I have brain storming on this and get three ideas..

1. Fix url is not my responsibility: Not care about urls compatablity. and assume that if users can find, use & download my app. they will also find the information they need... somehow through community (by ask on telegram community). and I just need care for some main url, like telegram community & passcodes website & of github url..

2. Take smart decision: take smart decision when add or share url, like share common url that like no gona change instead of one that prone to change. like not embedding url of file on main branch.. but have a version url for file. which break less often..

3. Url compatablity database: like put file on github that record all url.. and single source of truth when someone can look for how urls have are changed overtime.. like a url change history.. you know!!! (iykyk)

what do you think?

[JeelDobariya38]

2. Take smart decision: take smart decision when add or share url, like share common url that like no gona change instead of one that prone to change. like not embedding url of file on main branch.. but have a version url for file. which break less often..

https://github.com/PasscodesApp/Passcodes/blob/main/LICENSE.txt ❌

theroically, we can say that url below has less chance to break as it only break if repository link is migrated..
but this make the response not update on change.. this refer to file at that point.. and i think that take away the benifit of url... which make file dynamic...

https://github.com/PasscodesApp/Passcodes/blob/v1.1.1/LICENSE.txt ✅

[JeelDobariya38]

3. Url compatablity database: like put file on github that record all url.. and single source of truth when someone can look for how urls have are changed overtime.. like a url change history.. you know!!! (iykyk)

like this in markdown file in passcodes-docs repository.

# Link Migration DB


- https://github.com/JeelDobariya38/Passcodes -> https://github.com/PasscodesApp/Passcodes
- https://jeeldobariya38.github.io/Passcodes-Website -> https://passcodesapp.github.io/Passcodes-Website
- ... -> ...
- ... -> ...
- ... -> ...

[JeelDobariya38]

successfully closed by #5