Open easazade opened 2 months ago
Hey! So I've published two new packages: fhir_r4 and fhir_r5. The base package was growing too big. But these new versions include all of the other packages too. So they each have the base package, fhir_at_rest, fhir_auth, fhir_path, fhir_bulk, and fhir_db. They're also much smaller than the old version (partly because the main branch doesn't have any of the tests). And all of the dependencies should be easier now.
This is a suggestion: I saw
pubspec.yaml
file and the paths were set relatively. this will make it impossible to set the repo/fork of fhir_path as a dependency in flutter apps.I think if we structure code as mono-repo and use a mono-repo tool that enables bootstrapping and running custom scripts with defined scope on packages, would both solve the above mentioned problem and also make developing all these packages much easier. for the mono repo tool. i suggest melos which is widely used in dart/flutter community.