Skip to content
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

Merged
merged 5 commits into from
Feb 15, 2022
Merged

Conversation

zhen0
Copy link
Member

@zhen0 zhen0 commented Feb 10, 2022

Description

<! -- What is it meant to do? -->

Stop an odd artifact loading issue:

Screen Shot 2022-02-09 at 8 42 20 PM

Linked Issues

<! -- Use a key word (e.g. closes or resolves) to close related issues -->
Closes #1160

Tests and performance

  • Changes to any .js files are covered by existing tests or this PR adds new tests (if not please explain why below)
  • No new packages are added or package size and performance considerations are discussed below
  • PR Title fits our changelog format

Releases/Changelog cuts only

@zhen0 zhen0 marked this pull request as ready for review February 10, 2022 13:57
@@ -83,7 +83,7 @@ export default {
</script>

<template>
<v-row v-intersect="{ handler: onIntersect }" no-gutters>
<v-row no-gutters>
Copy link
Contributor

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

@zhen0 zhen0 changed the title remove v-intersect as it was causing odd behavior BugFix: Remove v-intersect as it was causing odd behavior Feb 15, 2022
@@ -38,9 +38,6 @@ export default {
},
increment() {
this.artifact++
},
onIntersect([entry]) {
this.$apollo.queries.artifacts.skip = !entry.isIntersecting
Copy link
Contributor

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

@zhen0 zhen0 merged commit 7e36403 into master Feb 15, 2022
@zhen0 zhen0 deleted the artifact-fix branch February 15, 2022 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: Artifacts loading incorrectly
3 participants