feat: simplify namespace search #1835
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#1835
Loading…
Reference in New Issue
No description provided.
Delete Branch "dpschen/frontend:feature/feat-simplify-namespace-selection"
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://1835-feature-feat-simplify-namespace---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!
It seems like the search does not work - the multiselect is missing completely:
@ -10,3 +10,3 @@
{{ $t('list.duplicate.text') }}
</p>
<namespace-search @selected="selectNamespace"/>
<Multiselect
Looks like you did not import the multiselect component.
Done
Would you mind adding a Cypress test for list duplication while we're at it?
1b09259239
to1f1abf083e
Can we see this branch as a bit more complex than necessary conversion to script setup?
Because I don't think it's a good idea to introduce tests to files where I would change much more if I would really rewrite instead of only convert them.
In this case e.g. aggregating the not component related logic somewhere.
Sure. I just figured if we had a test for this feature, the missing multiselect import could have been caught earlier 🙃
Now duplicating a list fails with this error:
1f1abf083e
to67c6f1ddca
The missing import would probably be catched by the improved vue linting.
But I get what you mean ;)
@konrad:
This is going in the direction I would like to create tests in the future:
#1800 (comment)
Would that be fine for you? And if yes can we merge this pull request?
Looks great!