这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@wawhal
Copy link
Contributor

@wawhal wawhal commented Feb 8, 2019

When you open the schema page on data tab in console, the suggested relations are generated with an iteration over a list and the key prop to each operator is the left-table of the suggested relation. In cases where relations for multiple tables are suggested, re-rendering is buggy because multiple elements have the same key and React looks at the key prop while performing incremental renders.

Description

What component does this PR affect?

  • Server
  • Console
  • CLI
  • Docs
  • Community Content
  • Build System

Requires changes from other components? If yes, please mark the components:

  • Server
  • Console
  • CLI
  • Docs
  • Community Content
  • Build System

Related Issue

Solution and Design

Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Docs update
  • Community content

Checklist:

  • I have read the contributing guide and my code conforms to the guidelines.
  • This change requires a change in the documentation.
  • I have updated the documentation accordingly.
  • I have added required tests.

@wawhal wawhal added k/bug Something isn't working c/console Related to console labels Feb 8, 2019
@wawhal wawhal requested a review from praveenweb February 8, 2019 13:11
praveenweb
praveenweb previously approved these changes Feb 8, 2019
@coco98
Copy link
Contributor

coco98 commented Feb 8, 2019

@wawhal @praveenweb you should specify which UI element is affected so that its easy to QA. Esp since this doesnt seem to be linked to an issue or is internally tracked.

@hasura-bot
Copy link
Contributor

Review app for commit f7b049c deployed to Heroku: https://hge-ci-pull-1578.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1578-f7b049c

@shahidhk
Copy link
Member

shahidhk commented Feb 9, 2019

@karthikvt26 One more review is required, esp. for functionality if it has to be verified. Please review.

@shahidhk shahidhk requested a review from karthikvt26 February 9, 2019 07:30
Copy link

@rikinsk-zz rikinsk-zz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Functionality looks good

@wawhal wawhal added the s/ok-to-merge Status: This pull request can be merged to master label Feb 11, 2019
@shahidhk shahidhk merged commit ca7e216 into hasura:master Feb 11, 2019
@hasura-bot
Copy link
Contributor

Review app https://hge-ci-pull-1578.herokuapp.com is deleted

hasura-bot pushed a commit that referenced this pull request Jan 31, 2025
<!-- The PR description should answer 2 important questions: -->

### What

Push down EXTRACT/DATE_PART function inside GROUP BY. Depends on
hasura/ndc-spec#201

### How

<!-- How is it trying to accomplish it (what are the implementation
steps)? -->

---------

Co-authored-by: Daniel Chambers <daniel@hasura.io>
V3_GIT_ORIGIN_REV_ID: ccff02132f05de0eb991967c56e0d23bbc69ccfd
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c/console Related to console k/bug Something isn't working s/ok-to-merge Status: This pull request can be merged to master

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants