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

Conversation

@rikinsk-zz
Copy link

Description

  • remove env var validation note from docs
  • change title of remote schema create errors

Affected components

  • Server
  • Console
  • Docs

Related Issues

Solution and Design

Steps to test and verify

Limitations, known bugs & workarounds

@rikinsk-zz rikinsk-zz added the s/do-not-merge Do not merge this pull request to master label Apr 2, 2019
@netlify
Copy link

netlify bot commented Apr 2, 2019

Deploy preview for hasura-docs ready!

Built with commit 6667f1e

https://deploy-preview-1932--hasura-docs.netlify.com

@rikinsk-zz
Copy link
Author

@tirumaraiselvan we need to update the error message returned by server in case of missing env var. It uses the phrase "custom resolver" which users dont know. Lets make int consistent with message for event triggers. The message there is generic enough. Similarly for any other error message we throw. remote schema instead of custom resolver needs to happen.
Screenshot from 2019-04-02 16-22-37

@tirumaraiselvan
Copy link
Contributor

@rikinsk The fix for that is in this PR: #1904

@hasura-bot
Copy link
Contributor

Review app for commit 6667f1e deployed to Heroku: https://hge-ci-pull-1932.herokuapp.com
Docker image for server: hasura/graphql-engine:pull1932-6667f1e

@rikinsk-zz rikinsk-zz merged commit 1c6e962 into hasura:master Apr 2, 2019
@hasura-bot
Copy link
Contributor

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

@rikinsk-zz rikinsk-zz deleted the remote-schema-errors branch April 2, 2019 11:14
@rikinsk-zz rikinsk-zz removed the s/do-not-merge Do not merge this pull request to master label Apr 3, 2019
hasura-bot pushed a commit that referenced this pull request Jun 4, 2025
so we don't get paged

<!-- The PR description should answer 2 important questions: -->

### What

<!-- What is this PR trying to accomplish (and why, if it's not
obvious)? -->

<!-- Consider: do we need to add a changelog entry? -->

<!-- Does this PR introduce new validation that might break old builds?
-->

<!-- Consider: do we need to put new checks behind a flag? -->

### How

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

V3_GIT_ORIGIN_REV_ID: 6cbc5b54d214b649633dc16482a54dfd85dff5dd
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.

4 participants