set up release

This commit is contained in:
Grahame Grieve 2024-04-17 06:21:22 +10:00
parent 461df3031b
commit 6ebbe2cb26
2 changed files with 41 additions and 7 deletions

View File

@ -1,7 +1,33 @@
## Validator Changes
* no changes
* Fix up path management in the validator for resolving references in Bundles
* Add support for defineVariable in FHIRPath
* Fix problem with CDA element having multiple types
* Fix problem with 'is' not working in FHIRPath for CDA types
* Fix issue processing CDA generic type names
* Fix for NPE processing tx server response
* Add support for code system supplements when communicating with tx server
## Other code changes
* no changes
* OSGI: make sure JUnit 4 and 5 dependencies are optional (#1596) (Also removed duplicate managed versions of JUnit 4.13.2 and mockwebserver 4.11.0)
* Render CapabilityStatement.imports (and instantiates)
* Terminology Service Tests - minor improvements for running in HAPI, add $lookup & $translate support, create R4 clone
* Add support for $translate to terminology client
* More i18n work in rendering context (WHO project)
* Add isServerSide for seeing if code systems are only supported on the server
* Fix R4B loading issue that lead to wrong web paths for R4B resources
* Fix problems rendering Binary files in IGs
* Add support for rendering logical URIs
* Remove path.toFile()
## Security
* Finish moving all local file access to go through ManagedFileAccess
## WHO Internationalization work
* More work on date rendering

View File

@ -3,17 +3,21 @@
# Local Filesystem
The main use of the local file system for the core library (other than the validator - see below) is for the
[NPM package cache](). The default location and content is as specified in the FHIR specification, bu you
can choose where this goes if you want, or provide your own NPM package cache manager
However there are other uses of the local file system scattered throughout the code. Long term,
the intention is to clean this up so these are all following a consistent policy.
[NPM package cache](https://confluence.hl7.org/display/FHIR/FHIR+Package+Cache). The default location and content
is as specified in the FHIR specification, but you can choose where this goes if you want, or provide your own NPM package cache manager. However there are other uses of the local file system scattered throughout the code, particularly in the test cases.
All access to the local file system runs through the class ManagedFileAccess. You can
set the static features of this class to completely cut the library off from the
local filesystem, or provide your own file system accessor, or limit the files accessed
to particular sub-directories. See ManagedFileAccess for details.
Note that libraries that this library depends on still access the filesystem directly. Review
of the use of these libraries is ongoing.
Validator: The validator CLI also accesses local files as specified in the command line parameters,
and runs in the user context. TODO: we are considering whether to support a command line parameter
restricting path access to particular directories.
# Network access
The library will access the web to download needed collateral, or to access terminology resources or servers.
@ -24,6 +28,10 @@ turn all network access off.
todo
# Terminology Server Access
todo
# Cryptography
Other than the https client, the library doesn't have any crypto functions in it.