fix: remove mentioning of context #1017
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#1017
Loading…
Reference in New Issue
No description provided.
Delete Branch "dpschen/frontend:feature/fix-translation-improvement"
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?
All other buttons on the task detail page also don't mention "this task" since that context is already given by the page you are on
Hi dpschen!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://1017-featurefix-translation-improvement--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!
Looks like the test is looking for "Assign this task to a user" - could you change it there to make it pass again?
Hahaha, I restarted the tests a few times and was really confused… explains a lot :D :D
44da9454cb
to4968d07d0e
Fixed. I had to downgrade to cypress 8. See: #1020
Also I added a directive that allows to select elements via a data attribute.
I used a directive so that the data attributes are only added when needed.
@ -273,2 +273,3 @@
type="secondary"
v-shortcut="'a'">
v-shortcut="'a'"
v-cy="'taskDetail.assign'"
This directive gets expanded to
data-cy="taskDetail.assign"
My idea was to use this pattern:
@konrad Can you help me with the
sed
? Locally this worked for me@ -0,0 +9,4 @@
const cypressDirective: Directive = {
mounted(el, {value}) {
if (
(window.CYPRESS_DATA_ATTRIBUTES === true || import.meta.env.DEV) &&
What about doing this with an env variable instead of another
window.
?I wanted to first. But then we would need to build it just for the tests again. Because the original idea of the directive is that there are no
data-cy
attributes in the final build when not needed.Or maybe just using
window.Cypress
?docs (it's not really documented this exists but it should work nevertheless)
I like that. Makes it much simpler =)
Fixed
Was wrong. Doesn seem to work yet :/
I think
window.cypress
might be undefined in the moment when the directive is mounted. Then it won't ever be added :/Bummer :/ I guess that's why it wasn't really documented.
Did you check if it is indeed not available when the directive is mounted? (Maybe with a
console.log(window.Cypress)
)That seems to be it.
4968d07d0e
to55f6af0214
@ -0,0 +9,4 @@
const cypressDirective: Directive = {
mounted(el, {value}) {
if (
(window.cypress || import.meta.env.DEV) &&
I think that should be
window.Cypress
with a capitalC
.Should have seen that…
55f6af0214
toa0abb3469e
Please resolve the conflicts
Feel free to merge once conflicts are resolved.
a0abb3469e
to199768f433