search

HL7 / fhir-ig-publisher

Source code for the IG publisher
Apache License 2.0
69 stars 57 forks source link

Duplicated Property Name issue #568

Closed kalleo1996 closed 1 year ago

kalleo1996 commented 1 year ago

image I am getting this error after updating the publisher , I even checked using different versions of the publisher , and figured out that I am getting error after FHIR IG Publisher Version 1.2.20 (Git# 2ac17a653f73) , please let me know if there something i can do from my side to get rid of this error .

grahamegrieve commented 1 year ago

what are your package dependencies. One of them has an error in it

On Fri, Dec 9, 2022 at 4:51 AM Threemana Hettige Kalpani Sewwandi < @.***> wrote:

[image: image] https://user-images.githubusercontent.com/38199192/206434167-5f9cda2e-220a-400c-be8e-fdf8a16100e1.png I am getting this error after updating the publisher , I even checked using different versions of the publisher , and figured out that I am getting error after FHIR IG Publisher Version 1.2.20 (Git# 2ac17a6 https://github.com/HL7/fhir-ig-publisher/commit/2ac17a653f733a863fd5a3074e5fe474b3c3e766) , please let me know if there something i can do from my side to get rid of this error .

— Reply to this email directly, view it on GitHub https://github.com/HL7/fhir-ig-publisher/issues/568, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMWKFNM2WLUD22675FG5NTWMINZZANCNFSM6AAAAAASYNM5YU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

--

http://www.healthintersections.com.au / @.*** / +61 411 867 065 Benson & Grieve: Principles of Health Interoperability (Health Information Technology Standards), 4th ed - http://www.springer.com/978-3-030-56882-5

kalleo1996 commented 1 year ago

these are the packages that have been used in the FHIR IG Publisher Version 1.2.19 image these are the json files of it . image image image image image image image

grahamegrieve commented 1 year ago

That's not enough information for me to chase down. I've added more logging for the next release

lmckenzi commented 1 year ago

Given no comments for over 6 months after additional logging was added, presume that the logging was sufficient to diagnose the problem and this is no longer an issue. If it remains a problem, please re-open.