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.

Sign up for GitHub

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

Jump to bottom

docs: add Hasura logo (fix #5934 ) #9059

Closed
wants to merge 2 commits into from
Closed

docs: add Hasura logo (fix #5934 ) #9059

wants to merge 2 commits into from

Conversation

anandgvb
Copy link
Contributor

@anandgvb anandgvb commented Oct 3, 2022

Using logo Hasura in README.md file (fix #5934)

Description

Using Hasura logo in README.md file that makes looks nicer

Changelog

Component : server / cli / console / build

Type: bugfix / feature / enhancement

Product: community-edition

Short Changelog

Long Changelog

Related Issues

Solution and Design

Steps to test and verify

Limitations, known bugs & workarounds

Server checklist

Catalog upgrade

Does this PR change Hasura Catalog version?

  • No
  • Yes
    • Updated docs with SQL for downgrading the catalog

Metadata

Does this PR add a new Metadata feature?

  • No
  • Yes
    • Does run_sql auto manages the new metadata through schema diffing?
      • Yes
      • Not required
    • Does run_sql auto manages the definitions of metadata on renaming?
      • Yes
      • Not required
    • Does export_metadata/replace_metadata supports the new metadata added?
      • Yes
      • Not required

GraphQL

  • No new GraphQL schema is generated
  • New GraphQL schema is being generated:
    • New types and typenames are correlated

Breaking changes

  • No Breaking changes

  • There are breaking changes:

    1. Metadata API

      Existing query types:

      • Modify args payload which is not backward compatible
      • Behavioural change of the API
      • Change in response JSON schema
      • Change in error code

    2. GraphQL API

      Schema Generation:

      • Change in any NamedType
      • Change in table field names

      Schema Resolve:-

      • Change in treatment of null value for any input fields

    3. Logging

      • Log JSON schema has changed
      • Log type names have changed

@anandgvb anandgvb requested a review from a team as a code owner October 3, 2022 18:02
@hasura-bot
Copy link
Contributor

Beep boop! 🤖

Hey @anandgvb, thanks for your PR!

One of my human friends will review this PR and get back to you as soon as possible.

Stay awesome! 😎

@CLAassistant
Copy link

CLAassistant commented Oct 3, 2022 •
edited
Loading

CLA assistant check
All committers have signed the CLA.

@marionschleifer marionschleifer added c/community Related to community content hacktoberfest labels Oct 6, 2022
hasura-bot added a commit that referenced this pull request Dec 21, 2022
@hasura-bot @anandgvb
docs: add Hasura logo (fix #5934 )
8eaaf81 
GITHUB_PR_NUMBER: 9059
GITHUB_PR_URL: #9059

PR-URL: hasura/graphql-engine-mono#6174
Co-authored-by: Anand Bhat <65865566+anandgvb@users.noreply.github.com>
GitOrigin-RevId: eb33d434eae74b4a6996d0f9cbcfe72f047ca8bd
@hasura-bot hasura-bot closed this Dec 21, 2022
@hasura-bot
Copy link
Contributor

Beep boop! 🤖

GIF

Awesome work @anandgvb!

Your changes were merged successfully. All of us at Hasura ❤️ what you did.

Thanks again 🤗

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
c/community Related to community content hacktoberfest merged
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@anandgvb @hasura-bot @CLAassistant @marionschleifer