Giter Club home page Giter Club logo

fhir-react's Issues

create Organization component

TODO:

  • Create scaffold of component
  • Add DSTU2 support to component
  • Add STU3 support to component
  • Add fixtures, tests, storybook stories

create Location component

TODO:

  • Create scaffold of component
  • Add DSTU2 support to component
  • Add STU3 support to component
  • Add fixtures, tests, storybook stories

create DocumentReference component

TODO:

  • Create scaffold of component
  • Add DSTU2 support to component
  • Add STU3 support to component
  • Add fixtures, tests, storybook stories

FhirResource Component

should allow any fhir resource to be inserted and display using the correct compoenent based on resourceType

create Appointment component

TODO:

  • Create scaffold of component
  • Add DSTU2 support to component
  • Add STU3 support to component
  • Add fixtures, tests, storybook stories

create Medication component

TODO:

  • Create scaffold of component
  • Add DSTU2 support to component
  • Add STU3 support to component
  • Add fixtures, tests, storybook stories

Remove dead code from fhir-react

I noticed the current size of fhir-react package is ~430KB (uncompressed).
This is way too big for a reusable package.

AFAICT, the main culprits are:

  • lodash package, which is being imported in entirety, even though we use only a few utilities.
  • crypto package, also imported whole even though we just use the MD5 hash function.

TODO:

create Questionnaire component

TODO:

  • Create scaffold of component
  • Add DSTU2 support to component
  • Add STU3 support to component
  • Add fixtures, tests, storybook stories

create ReferralRequest component

TODO:

  • Create scaffold of component
  • Add DSTU2 support to component
  • Add STU3 support to component
  • Add fixtures, tests, storybook stories

Set up tests in fhir-react

  • Set up jest and react-testing-library in fihr-react.
  • Add a few example tests.
  • Run the tests during CircleCI build.

create CareTeam component

TODO:

  • Create scaffold of component
  • Add DSTU2 support to component
  • Add STU3 support to component
  • Add fixtures, tests, storybook stories

create Coverage component

TODO:

  • Create scaffold of component
  • Add DSTU2 support to component
  • Add STU3 support to component
  • Add fixtures, tests, storybook stories

create MedicationRequest component

TODO:

  • Create scaffold of component
  • Add DSTU2 support to component
  • Add STU3 support to component
  • Add fixtures, tests, storybook stories

create ClaimResponse component

TODO:

  • Create scaffold of component
  • Add DSTU2 support to component
  • Add STU3 support to component
  • Add fixtures, tests, storybook stories

Set up code linter in fhir-react

  • Set up eslint & prettier for fihr-react.
  • Add lint and lint:fix tasks to package.json that will check and automatically fix code formatting.
  • Fix the formatting and lint violations of the entire codebase.
  • Add the lint step to CircleCI build, so it will fail when code is malformed.

Recommended eslint config: see what create-react-app uses https://www.npmjs.com/package/eslint-config-react-app
https://www.npmjs.com/package/eslint-config-prettier
https://www.npmjs.com/package/eslint-plugin-prettier

Example .eslintrc config:

{
  "extends": [
    "react-app",
    "prettier"
  ],
  "plugins": [
    "prettier"
  ],
  "rules": {
    "semi": "error",
    "prettier/prettier": "error",
  }
}

Improve the style architecture

The current state of styling in fhir-react is a mix of inline styles and bootstrap.
It is not very readable, a bit inconsistent and not extensible by users.

Here's our idea to improve the architecture:

  • Consistency: write regular CSS files for styles, instead of inline/bootstrap combo.
  • Extensibility: use BEM-style class names e.g. .fhir-ui__Value, fhir-resource__Observation. Consumers will be able to override these classes with their own styles.
  • Lessen the dependency on bootstrap (avoid using its classes and utilities).

TODO:

  • Style components in src/components/ui
  • Style components in src/components/resources
  • Style components in src/components/container
  • Style components in src/components/datatypes
  • Optional: export one stylesheet for consumers to import (e.g. via webpack)

create Claim component

TODO:

  • Create scaffold of component
  • Add DSTU2 support to component
  • Add STU3 support to component
  • Add fixtures, tests, storybook stories

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.