Uploaded image for project: 'mod-graphql'
  1. mod-graphql
  2. MODGQL-132

The current Docker configuration for mod-graphql will not start

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: TBD
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.5.0
    • Labels:
      None
    • Template:
    • Development Team:
      None

      Description

      As pointed out by Maksym Sinichenko in a Slack conversation, trying to start mod-graphql with the configuration used by the Dockerization currently fails:

      mod-graphql$ rm -rf tests/input
      mod-graphql$ ./tests/setup.sh
      Setting up API data ...
      [...]
      ... all done
      mod-graphql$ yarn start tests/input/*/ramls/*.raml
      yarn run v1.22.5
      $ babel-node --presets=env,stage-2 main.js tests/input/mod-inventory-storage/ramls/alternative-title-type.raml ...
      [...]
      /Users/mike/git/folio/other/mod-graphql/src/autogen/mergeAPIs.js:93
                throw Error('duplicate type name \'' + name + '\' with different definitions in ' + register[name] + ' and ' + ramlName);
                ^
      Error: duplicate type name 'T_raml_util_schemas_resultInfo_schema' with different definitions in tests/input/mod-inventory-storage/ramls/holdings-storage.raml and tests/input/mod-users/ramls/users.raml
          at /Users/mike/git/folio/other/mod-graphql/src/autogen/mergeAPIs.js:77:17
      

        TestRail: Results

          Attachments

            Activity

              People

              Assignee:
              mike Mike Taylor
              Reporter:
              mike Mike Taylor
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  TestRail: Runs

                    TestRail: Cases