Closed glenarama closed 6 months ago
Yep. I already know about this... I have yet to get around to it.
Got it working..
Release coming very shortly.
:tada: This issue has been resolved in version 2.1.0-beta.2 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
@glenarama Can you check this out in the development release?
Looks to be working @Bugs5382 Thanks!
Theres an issue with ES6 import recognition, but it is working.
Can you try:
import {HL7_2_2} from "node-hl7-client/lib/types/hl7";
I am looking for an NPM package that does this type of "sub" package as a typescript. Not sure the above is the best method.
That didn't help, could you not just export them at the top level? They would get shaken out when not used.
Yeah. I just ran a test on one of the apps I am doing.. which I am using 2.7 ... so ok. Let me re-work this tonight. :)
So, going over the code, I can't merge it into the main thing; otherwise, things will break. Yikes. So, I gotta figure out this sub-module issue.
Ok. I got it working in my code now....
import {HL7_2_3} from "node-hl7-client/hl7"; now will work in upcoming develop channel.
2.1.0-beta.3 is out. Please try it there...
import {HL7_2_2} from "node-hl7-client/hl7"
console.log(new HL7_2_2())
Looks good! Thanks.
@glenarama - let me know so I can push it out to main. :)
@glenarama - let me know so I can push it out to main. :)
Its working good for me now thanks.
:tada: This issue has been resolved in version 2.1.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Need to be able to create versions other than 2.7
Currently the example shows creation using:
specification: new HL7_2_3()
However the HL7 versions are not exported, so 2.7 is used by default. This then forces 9 to have a secondary constructed ADT message which breaks the 2.2 server im trying to communicate with.
Could HL7_2* be exported or added as a messageHeader option?