feat NewNamespace script setup #2415
No reviewers
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
3 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#2415
Loading…
Reference in New Issue
No description provided.
Delete Branch "dpschen/frontend:feature/feat-NewNamespace-script-setup"
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 changes of this PR on a preview environment under this URL: https://2415-feature-feat-newnamespace-script--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 somehwere. The easiest to use is https://try.vikunja.io/.
Have a nice day!
Trying to create a new namespace results in an error message:
But the namespace is still created.
Yes. I think that was an issue all along but just got obvious now that it's converted to script setup. See
b24e9725fa/src/views/namespaces/NewNamespace.vue (L15)
The
back
function was not defined in the old version as well.Not sure what the intend here is. I guess you meant to write
$router.back
, but it seems weird to use that on the input field, since it changes the view aka closes the whole component.It should be
$router.back()
. The idea was that you could close the modal by pressing escape - that already works with the default modal but with the input modal here since it autofocuses the input that input field catches the focus instead. Hence I just placed the listener on the input field directly.That makes sense. Will fix!
b24e9725fa
todbbbc1cc32
@konrad Fixed
This seems to be still a problem.
dbbbc1cc32
to8cca569677
Sorry…
I fucked up with rebasing and only submitted the fixes but not the original request :D
Should work now.
Seems to work fine now.