FHIR/fhir.js

Middleware Error Trace Produced In Docker

Open

#129 opened on Nov 2, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (142 forks)auto 404
buggood first issue

Repository metrics

Stars
 (437 stars)
PR merge metrics
 (PR metrics pending)

Description

Version 0.0.20 Platform Linux(Ubuntu) Docker Container

Hey I'm trying to running a smart client on one of lx boxes and the following ugly stack trace is outputed

     Cannot read property 'trim' of undefined
     at buildPathPart (/app/checkItOut/node_modules/fhir.js/src/middlewares/url.js:33:30)
     at new_chain (/app/checkItOut/node_modules/fhir.js/src/middlewares/url.js:45:62)
     at new_chain (/app/checkItOut/node_modules/fhir.js/src/middlewares/url.js:45:32)
     at /app/checkItOut/node_modules/fhir.js/src/middlewares/core.js:67:30
     at /app/checkItOut/node_modules/fhir.js/src/middlewares/core.js:58:28
     at /app/checkItOut/node_modules/fhir.js/src/middlewares/core.js:58:28
     at /app/checkItOut/node_modules/fhir.js/src/middlewares/core.js:58:28
     at /app/checkItOut/node_modules/fhir.js/src/middlewares/http.js:27:20
     at /app/checkItOut/node_modules/fhir.js/src/middlewares/core.js:56:28
     at /app/checkItOut/node_modules/fhir.js/src/middlewares/core.js:58:28

Anyone else getting this?

Contributor guide

Research direction
Inspect the middleware chain in fhir.js, particularly the url.js middleware, to identify where an undefined value is passed to trim(). Trace the call path from core.js to find the root cause.
Tech stack
javascript
Domain
backendapi
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60