tricoder42

export const fetchSaga = (entity, api) => function* ({ payload }) {
  try {
    const data = yield call(api, payload)
    yield put(entity.response(data))
  }
  catch(error) {
    // When there's error.response, it's usually response from
    // backend server with status 4xx or 5xx.
    // No response mostly means there's a connection error, because
    // we don't even get anything from server.

tricoder42

// Just an example of `isAuthenticated` selector
const selector = {
  isAuthenticated: state => state.auth.isAuthenticated
}

export const authRequired = (saga) => function* (action) {
  const isAuthenticated = yield select(selector.isAuthenticated)

  // If user isn't authenticated, redirect him to /login
  if (!isAuthenticated) {

tricoder42

// load() call is removed, but import remains there

!function(modules) {
    function __webpack_require__(moduleId) {
        if (installedModules[moduleId]) return installedModules[moduleId].exports;
        var module = installedModules[moduleId] = {
            i: moduleId,
            l: !1,
            exports: {}
        };

tricoder42

{
  "Edit": {
    "translation": "Upravit",
    "origin": [
      [
        "src/lingui/projects/scenes/Repository/ui/EditableDescription.js",
        81
      ]
    ]
  },

tricoder42

class ProjectType(graphql.DjangoModel):
    class Meta:
        model = Project


class ProjectSchema(graphql.DetailQuery,
                    graphql.ListQuery,
                    graphql.CreateMutation,
                    graphql.UpdateMutation,
                    graphql.DeleteMutation,

tricoder42

GraphQL Subscription with django-channels

Django channels are official way for implementing async messaging in Django.

The primary caveat when working with GraphQL subscription is that we can't serialize message before broadcasting it to Group of subscribers. Each subscriber might use different GraphQL query so we don't know how to serialize instance in advance.

See related issue

tricoder42

GraphQL example

Graphene Tutorial

Example of authentication mutations and user queries in GraphQL API.

tricoder42

const flip = () => ({
  flipResults: Math.random()
})

// creation of headlesscomponent
class CoinFlip extends React.Component {
  state = flip()
  handleClick = () => this.setState(flip)
  
  api() {

tricoder42

/*
Usage: node ./deprecate.js OTP_TOKEN

OTP_TOKEN is used for 2FA
*/

const path = require("path")
const fs = require("fs-extra")
const { exec } = require("child_process")

tricoder42

1. Query projectIssue is resolved with an object "IssueType:18"
2. Mutation issueEdit is called and returns the same object with updated attachments
3. Object "IssueType:18" is updated correctly in cache (checked in Apollo DevTool and also manually by store.readFragment)
4. Query projectIssue reloaded from cache automatically, but this this it doesn't return object

In Apollo DevTool I see this field in root query: issue({"issueId":"18","project":"IEP001"}): IssueType:18. I believe the query should be updated when object IssueType:18 in cache is updated, but when it happens, the object is empty.