You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we're starting to include deep links to the lit.dev docs site from DEV_MODE warnings, it seems likely that we're bound to break these links in the future if we're not careful (since user-pinned code versions can live forever while lit.dev content is bound to evolve over time).
I propose we replace deep links embedded in code with a shortened URL scheme which can be easily redirected on the lit.dev site without worrying about how URLs on the site may evolve in the future. This would also have the side-benefit of having a central place on the lit.dev site that catalogs all pages that are referred to via code.
As we're starting to include deep links to the lit.dev docs site from DEV_MODE warnings, it seems likely that we're bound to break these links in the future if we're not careful (since user-pinned code versions can live forever while lit.dev content is bound to evolve over time).
I propose we replace deep links embedded in code with a shortened URL scheme which can be easily redirected on the lit.dev site without worrying about how URLs on the site may evolve in the future. This would also have the side-benefit of having a central place on the lit.dev site that catalogs all pages that are referred to via code.
Example:
lit.dev/msg/render-method-removed
->https://lit.dev/docs/releases/upgrade/#litelement
lit.dev/msg/multiple-versions-loaded
->https://lit.dev/docs/tools/adding-lit/#multiple-versions
...
The text was updated successfully, but these errors were encountered: