test: unit test succeeds
fix: not quiting loop when releasing unexisting lock
refactor: pull wait() function into TimerUtils
feat: store all locks inside a single lock folder
feat: use md5 hashing for filepath hashes
test: coverage back to 100%
fix: store locks in proper .internal/locks folder
feat: reworked tryfn
test: coverage back to 100%
buidl: package json types next to lib
style: linting
dos: add more documentation to Locker classes
refactor: SingleThreadedResourceLocker -> MemoryResourceLocker
refactor: MultiThreadedResourceLocker -> FileSystemResourceLocker
feat: update all file-based backend configs to use the new FileSystemResourceLocker
feat: add warning on starting the MemoryResourceLocker in a worker process
test: coverage back to 100%
fix: finalizer of file.json was configured wrong
docs: updated release notes for 5.0.0
refactor: incorporated changes so far
refactor: retryFunctions are less complex now
test: jitter fix
* feat: (AppRunner) Mechanism to configure cli args and derive componentsjs vars from them implemented
* fix: (AppRunner) tidying
* fix: (AppRunner) tidying up
* fix: (AppRunner) runCli method made sync
* fix; (VarResolver) refactored to multiple files, and other stylistic fixes.
* chore: (AppRunner) Uses builder pattern for yargs base arguments setup to enable better typescript inference
* fix(AppRunner): refactoring AppRunner and VarResolver
* fix(AppRunner): refactoring AppRunner promise handling
* fix(AppRunner): verror dependency removal
* fix: Simplify CLI error handling
* feat: Use same config for both CLI and app instantiation
* fix: Update typings and imports
* feat: Split VariableResolver behaviour to 2 classes
* feat: Move default value behaviour from CLI to ValueComputers
* test: Add unit tests for new CLI classes
* feat: Integrate new CLI configuration with all default configurations
* feat: Add createApp function to AppRunner
* docs: Update comments in CLI-related classes
* fix: Various fixes and refactors
Co-authored-by: damooo <damodara@protonmail.com>
Configuration has been updated so the IDP requests
also pass through an Authorization component.
A new config option was added to choose
which authorization scheme to use for the IDP.
This required AuxiliaryStrategy to have a new function
indicating if the auxiliary resource just used its associated resource authorization
or its own.
This adds options for enabling setup to the config folder.
All default configs with permanent storage (file/sparql)
are configured to require setup at server start.
Memory-based configs merely have it as an option.
