feat: inline dynamic component definitions in routes #2812
Reference in New Issue
Block a user
No description provided.
Delete Branch "feature/inline-dynamic-routes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi dpschen!
Thank you for creating a PR!
I've deployed the frontend changes of this PR on a preview environment under this URL: https://2812-feature-inline-dynamic-routes--vikunja-frontend-preview.netlify.app
You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somewhere. The easiest to use is https://try.vikunja.io/.
This preview does not contain any changes made to the api, only the frontend.
Have a nice day!
Looks like the tests are now failing
98ccfd7e79
to0211d70af1
0211d70af1
to6605dcbcf3
@konrad Do you have any ideas regarding the failing pipeline here?
I think I'm blocked on #2950 for the same reason because it's based on this PR.
The issue seems to be a timing problem. Specifically,
LinkSharingAuth
is now being loaded dynamically, whereas it was synchronous before. Because of this, something is failing. Since I don't fully understand the authentication mechanism (it's spread across many files), I haven't been able to debug it. I've tried several times but just can't make progress.Does it work if the link share auth is loaded synchronous?
6605dcbcf3
todb16ad21ff
9cf1ca8860
to6203155080
6203155080
to356e83a6c9
Seems to work, but loading routes async is a requirement for using that route via unplugin-vue-router
@ -211,3 +158,3 @@
path: '/share/:share/auth',
name: 'link-share.auth',
component: LinkShareAuthComponent,
// FIXME: use dynamic imports
Maybe add a comment why this isn't using a dynamic import?
As written before:
So for #2950 sadly this is still not a real solution.
For me this seems to be a race condition in the auth implementation.
Any ideas?
I think it's fine to include this in the bundle, but a comment saying "we're including this in the bundle because" is better than a
FIXME
:)356e83a6c9
to7e787c9a3b