-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BugFix: Remove v-intersect as it was causing odd behavior #1224
Conversation
@@ -83,7 +83,7 @@ export default { | |||
</script> | |||
|
|||
<template> | |||
<v-row v-intersect="{ handler: onIntersect }" no-gutters> | |||
<v-row no-gutters> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we might as well remove the onIntersect method above as well
@@ -38,9 +38,6 @@ export default { | |||
}, | |||
increment() { | |||
this.artifact++ | |||
}, | |||
onIntersect([entry]) { | |||
this.$apollo.queries.artifacts.skip = !entry.isIntersecting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stackoverfloweth you would understand the behavior this was meant to support a bit better but does removing this have performance implications? I wonder if modifying this intersection method to match the behavior of the defined skip on the query would be better instead
Description
<! -- What is it meant to do? -->
Stop an odd artifact loading issue:
Linked Issues
<! -- Use a key word (e.g. closes or resolves) to close related issues -->
Closes #1160
Tests and performance
Releases/Changelog cuts only