Package Exports
- @forrestjs/service-hasura-client
- @forrestjs/service-hasura-client/src/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@forrestjs/service-hasura-client) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Hasura Client for NodeJS
Configuration
forrest.run({
settings: {
hasura: {
endpoint: 'http://localhost:8080',
secret: 'hasura',
auth: {
token: 'token',
jwt: {
secret: 'abc',
roles: ['r1', 'r2'],
defaultRole: ['r1'],
session: {
foo: 'bar'
}
},
fn: async () => ({
token: 'token',
ttl: 0
})
}
}
}
})👉 Only one auth setting is supported at any time.
Authorization Token
When you provide this setting, HasuraClient will use it as Authorization: Bearer {token}.
Authorization JWT
[[ TO BE IMPLEMENTED ]]
When you provide this setting, HasuraClient will calculate the JWT and use it as Authorization: Bearer {jwt}.
Authorization Logic
[[ TO BE IMPLEMENTED ]]
When you provide this setting you can calculate the authorization token by offering a custom logic.
- the resulting
tokenkey will be used asAuthorization: Bearer {token}. - the
ttlwill be used as cache flag:0keep forever (until reboot)-1calculate at every query1000keep for 1s (integer value expressed in milliseconds)
Query
const MY_QUERY = `
query FooBar ($var: String!) {
resource (
par: $var
) {
field1
field2
}
}
`;
const myFeature = () => [{
target: '$START_FEATURE',
handler: async ({ getContext }) => {
const hasura = getContext('hasura');
const res = await hasura.query(MY_QUERY, {
var: 'foobar'
});
console.log(res);
}
}];Sql
const myFeature = () => [{
target: '$START_FEATURE',
handler: async ({ getContext }) => {
const hasura = getContext('hasura');
const res = await hasura.sql(MY_QUERY, {
var: 'foobar'
});
console.log(res);
}
}];