-
-
Notifications
You must be signed in to change notification settings - Fork 365
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
fix: Empty swap table with valid swaps #11299
Conversation
✅ Deploy Preview for koda-canary ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
- add: cloneRawObject - add: override param
- allow `useGrapqh` to be used outside setup , fix [Graphql Subscription] Polling error: Error: vue-query hooks can only be used inside setup() function or functions that support injection context.
- removed: mapToId util - removed: existingCollectionList query
- simple solution to ensure only the latest query result updates the state.
@preschian any idea why the preview link is not working? |
Quality Gate passedIssues Measures |
is not showing the skeleton first better and then fallback to the empty message? |
hhmm, this is new for me. seems like need to check it through netlify dashboard cc @vikiival |
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.
Anyway, are you able to create a branch directly in kodadot/nft-gallery instead of branching from a fork?
This would allow us to see the deployment preview through Cloudflare Pages, since currently we're not able to see the deployment preview from Netlify. At the moment, Cloudflare Pages doesn't support deployment previews from forked branches
...extraVariables, | ||
}, | ||
clientId: isRef(client) ? String(client.value) : client, | ||
const requestId = ++currentRequestId.value |
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 probably don't need the useGraphql
composable at all. I prefer using useQuery
directly from NuxtApollo instead - that composable alone might be sufficient
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.
Yep, I like this solution a lot better. new pr #11303
import { mapToId } from '@/utils/mappers' | ||
import { unwrapSafe } from '@/utils/uniquery' | ||
|
||
export function useNewCollectionId() { |
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.
nit: let's move to separate PR regarding remove unused stuff
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.
sure
closing in favour of #11303 |
PR Type
Context
Adds the ability to pass
variables
asref
touseGraphql
reviewers kindly also test , tyvm
useNewCollectionId
Screenshot 📸