cql-execution port to ES6... about clinical_quality_language

[cmoesel]

Hi Jeff,

I think this sounds awesome. After taking a long break from anything Javascript related, I've recently come back and found that I really like ES6 -- and some of the great tooling that's been built around ES6. If I was writing cql-execution today, I'd certainly write it in ES6!

That said, we have a team that's already invested in the Coffeescript version (and is using Coffeescript elsewhere in their app). They are a bit reluctant, at this point, to take on the risk of a full translation into ES6. That may change, but that seems to be where things stand now.

But... I'd personally love to see your ES6 implementation. Any chance you could grant me access so I could poke around and see how it works?

[turp1twin]

Hey Chris,

Yeah, sounds good. I will give you access. It is still a work in progress, and there are a few bits that I still need to work out. That being said, I tried to stay as close to the structure you have in the coffee project, but might start to reorganize things a bit more... Anyways, have a play...

Jeff

[seanknox]

Hey @turp1twin, the Able Health team would love to participate if possible. Shoot me an email if you're interested: [email protected].

[turp1twin]

Hey @seanknox, glad to get you involved. Will send you an email with some details...

Jeff

[preston]

+1 to either ES6 or TypeScript-based canonical version. CoffeeScript was great while it lasted, but just isn't needed anymore.

[preston]

@turp1twin Hi Jeff: any chance you may be able to make your version of the project available soon?

[turp1twin]

Hey @preston I'll open it up later today. That being said, it needs some love, looking forward to contributions....

[preston]

@turp1twin Right on... do you think it's in a functional enough state to be suitable for npm packaging/release as well?

For context, I'm a contributor to the CQF Knartwork project, and would love to be able to integrate these libraries either directly or through a web service interface.

[turp1twin]

@preston The unit tests all run, but that is about all I have done with it so far. My day job has been keeping me crazy busy. The readme definitely needs updating for sure, before doing an NPM release....

[turp1twin]

@preston The repository is public now...

[rdingwell]

@preston as long as the port didn't change any of the api name spacing or method signatures you should be able to get started with the cql-execution npm package that is already published and built from the coffeescript version of the library.

https://www.npmjs.com/package/cql-execution

[brynrhodes]

This issue was moved to cqframework/cql-execution#47