npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

prettier-plugin-fhirpath

v0.0.1-alpha-2

Published

Prettier plugin for FHIRPath

Downloads

1

Readme

prettier-plugin-fhirpath

Prettier plugin for FHIRPath language using ANTLR4 grammar

Installation

yarn add --dev prettier-plugin-fhirpath

Configuration

In .prettierrc.js

    ...
    plugins: ["prettier-plugin-fhirpath"]
    ...

Formatting rules

There are no general rules are described for the moment anywhere, so based on the experience of writing quite long and complex expressions there are some rules of formatting introduced for better readability:

  • Parentheses content should be split by new lines if the content length is more than N characters or more than one argument is used in the function

Should not be formatted with new lines:

repeats(item)

(1 + 1)

where(code = 'value')

Should be formatted with new lines:

iif(
    %var > 1,
    1,
    2
)

where(
    code = %var.very.long.path.to.the.value
)
  • Binary operator should be split by new lines if the total length is more than N characters

Should not be formatted with new lines:

code in 'a' | 'b' | 'c'

Should be formatted with new lines:

code in 'very-long-code-first' | 
    'very-long-code-second' | 
    'very-long-code-third'
  • Spaces around operators and keywords always should be used
where(code = 'value1' or code = 'value2')

1 + 1 / 1

Supported extensions

  • .fhirpath
  • .yaml (embedded inside expression)

Future plans

  • .jsx?/.tsx? (embedded inside fhirpath template)
  • FHIRPath Mapping Language embedded support inside {{ }} and etc
  • FSH embedded support inside [[ ]]

Release Notes

0.0.1 (in development)

  • Initial release