Skip to content

Conversation

@Quarz0
Copy link

@Quarz0 Quarz0 commented Oct 30, 2025

resolve() should not require the Reference.type field to be specified

This PR also adds proper handling for fragment and uri references, also skips empty strings from being passed to the resolver.

Also introduced a SimpleResolver to improve the test coverage - current tests only relied on HappyResolver which just returns without checking any references. If we remove the references from the current tests they'd still pass

AlexJSully added a commit that referenced this pull request Nov 13, 2025
This PR includes the following:

- #27 by Marwan Tammam
(@Quarz0) & integrated by Vicknesh Suresh (@VickSuresh)
- #30 by Marwan Tammam
(@Quarz0) & integrated by Alexander Sullivan (@AlexJSully)
- Go version and packages update by Arthur Pang (@arthurpang) 
- Go decimal package update by Joel Phillip (@joelphillip1)
- Update for handling extensions by Bharath Vemula (@bharath-v1)

GitOrigin-RevId: 65cbe989a46576d9ba6ee97a8d3b98a066515888

Co-authored-by: Copybara <copybara@example.com>
@AlexJSully
Copy link
Member

Hi @Quarz0,

Thank you so much for your contribution and for taking the time to implement 'resolve' and improve test coverage! We truly appreciate your effort and the quality of your work.

At this time, we’re not able to accept public pull requests directly (though we hope to support this soon—stay tuned!). However, we want to make sure great contributions like yours are recognized and included. We’ve backported your implementation (#33), and it will be included in the next version release of FHIRPath Go. You will be credited in the release notes for your work.

Thanks again for helping make this project better!

@AlexJSully AlexJSully closed this Nov 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants