knight/datahub
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[catalog/queries][s]: optimized the way we query graphql so that we only use single query for dataset/resource pages. It also fixes some buggy behaviour of next.js described in https://github.com/vercel/next.js/issues/8563.

Browse Source
This commit is contained in:
anuveyatsu
2021-08-24 12:15:03 +06:00
parent 6bc36f9e3b
commit feb1fd62f4
6 changed files with 17 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
examples/catalog/components/resource/About.tsx
View File

@@ -1,11 +1,11 @@
/* eslint-disable react/display-name */
import { useQuery } from '@apollo/react-hooks';
import { ErrorMessage } from '../_shared';
import { GET_RESOURCES_QUERY } from '../../graphql/queries';
import { GET_DATASET_QUERY } from '../../graphql/queries';
import { ResourceInfo } from 'portal';
const About: React.FC<{ variables: any }> = ({ variables }) => {
const { loading, error, data } = useQuery(GET_RESOURCES_QUERY, {
const { loading, error, data } = useQuery(GET_DATASET_QUERY, {
variables,
// Setting this value to true will make the component rerender when
// the "networkStatus" changes, so we are able to know if it is fetching

4
examples/catalog/components/resource/DataExplorer.tsx
View File

@@ -1,9 +1,9 @@
import { useQuery } from '@apollo/react-hooks';
import { ErrorMessage } from '../_shared';
import { GET_RESOURCES_QUERY } from '../../graphql/queries';
import { GET_DATASET_QUERY } from '../../graphql/queries';
const DataExplorer: React.FC<{ variables: any }> = ({ variables }) => {
const { loading, error, data } = useQuery(GET_RESOURCES_QUERY, {
const { loading, error, data } = useQuery(GET_DATASET_QUERY, {
variables,
// Setting this value to true will make the component rerender when
// the "networkStatus" changes, so we are able to know if it is fetching