stefanwalther / qix-graphql Goto Github PK

The beauty of GraphQL is that it works with many programming languages. Let's provide some examples with the most popular languages.

• Basic code example
• Test
• Integrate test into CircleCI

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Environment mode:

• / - Basically just showing HATEOAS links, later on some basic UI
• /env/graphiql/ - Starting graphiql for the env mode

App mode:

• /app/:id/graphiql/- GraphiQL for the specifc app

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Attempting to follow the installation and usage instructions on the README to get started, docker-compose up fails because the compose file relies on an environment variable QIX_ENGINE_VER:latest:

from docker-compose.yml:

qix:
    container_name: qix
    image: "qlikcore/engine:${QIX_ENGINE_VER:latest}"
    command: [
      "-S", "DocumentDirectory=/docs",
      "-S", "AcceptEULA=yes"
    ]

The beauty of GraphQL is that it works with many programming languages. Let's provide some examples with the most popular languages.

• Basic code example
• Test
• Integrate test into CircleCI

Currently, it appears that when you use this package, it spins up its own Core instance and hooks into that to give you access to GraphQL queries for that specific instance. Is there a way to leverage that GraphQL query layer with any Core instance? That would be much more desirable to me. For example, I've got several Core containers running on my machine related to various projects. I'd love to leverage the GraphQL query layer as an independent service that I can use with any of those instances as needed.

Currently the different data types are not handled properly, this needs to be fixed and tested.

It would be interesting to run the GraphQL server in two different modes (based on configuration):

• Stateful
  • ws connection remains open
  • user can make selections
  • can get current selections
  • can execute a chain of commands
  • etc.
• Stateless
  • always opening, closing, re-opening the ws-connection
  • do not allow the user to make selections
  • some mutations and queries should then just not be available
  • Basically the GraphQL server acts then like a connector to fetch data easily from a Qlik app

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

The beauty of GraphQL is that it works with many programming languages. Let's provide some examples with the most popular languages.

• Basic code example
• Test
• Integrate test into CircleCI

Get rid of some hardcoded/fake code from the prototyping work, especially in

• ./qix-resolvers.js
• Engine location: localhost
• Engine port
• QIX schema ???!

• Motivation
• Background information / Key concepts
  • What is GraphQL
  • GraphQL Community / eco-system / programming languages
  • GraphiQL
• Examples
  • node.js
  • go
  • Python
  • C#
• How to set up
  • A demo environment
  • Dependencies
  • Run tests
  • Watchers

• Basic CircleCI integration for both unit and integration tests

The beauty of GraphQL is that it works with many programming languages. Let's provide some examples with the most popular languages.

• Basic code example
• Test
• Integrate test into CircleCI

On the doc scope it would be nice to provide a query, returning all data tables and keys.

Code:

• Move to async/await
  • ./app-server.js
• Remove the /docs endpoint
• Remove/Rename ./modules/app/sample-schema.js
• health-check
• Remove package-lock.json
• Handle all Todo (AAA)
• Rename modules to match resource thinking / endpoints
• File ./prototyping-to-be-moved.js

Tests:

• Simplify tests by moving to async/await
• Removes logging from tests

Describe the bug
When following along with the README, it shows how you can use

_links {
  _doc
}

to get a url to a GraphiQL instance connected to a specific doc. In the README, the example gets hosted locally at localhost:3004. However, the response url that the API provides references qix-graphql instead of localhost as the host. Ex:

{
  "data": {
    "doc": {
      "_links": {
        "_doc": "http://qix-graphql:3004/app/%2Fdocs%2FConsumer%20Goods%20Example.qvf/graphql"
      }
    }
  }
}

To Reproduce
Steps to reproduce the behavior:

1. Follow the instructions on the README to spin up GraphiQL
2. Run a query like so to get the link for a doc:

{
  doc(qDocId: "/docs/Consumer Goods Example.qvf") {
    _links {
      _doc
    }
  }
}

3. Look at the URL that is returned by the API call

Expected behavior
The URL should reference localhost as the host, not qix-graphql.

The docs/apps identifier starts right now with ./docs, which is completely silly and unnecessary.

The qix-schema is now hardcoded, but it actually should be dynamic based on the engine version.
Really not sure how to handle this the best way.

This probably sounds abit random but what extra value does qlik add to a project if your already using GraphQL? GraphQL is basically its own associative engine right? Im just struggling to think why would need Qlik if your already familliar with GraphQL.

• Use CircleCI to send the code-coverage results to CodeCov.

Implemented in #22

See PR #20

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.