(apply-policy-targets {:deps/keys [type apply-library-editor ->library-version
->sha ->data ->name]}
{:keys [project configurations fingerprints] :as request})
returns a channel which will emit a :complete value after applying all version policies to a Repo Steps are roughly
params apply-target-fingerprint (project,target-fingerprint) => channel emitting logged message
returns a channel which will emit a :complete value after applying all version policies to a Repo Steps are roughly - use configuration to construct the Policy to apply - emit plan elements from a version-channel (which may fetch live latest data from the graph) - check whether any current fingerprint are off target - apply plan elements that represent off-target deps inside of a PR editor params apply-target-fingerprint (project,target-fingerprint) => channel emitting logged message
(deps-handler data
sendreponse
&
{:deps-command/keys [show sync update]
:deps/keys [extract validate-policy validate-command-parameters]
:as contract})
- VIEW COMMAND setup a command to compute and show fingerprints in slack just-fingerprints runs on a cloned repo and just shows data in Slack - does not send fingerprints - SYNC COMMAND using configuration policy - setup a sync command compute-fingerprints will compute and send fingerprints, and mw-validate-policy will ensure configuration is in a good state - UPDATE COMMAND using cli params (does not apply cofiguration policy) compute-fingerprints will compute and send fingerprints and validate-parameters will check the command line parameters (this does not apply the policy in the configuration but instead sets up a new one based on the parameters - finally, set up a Push event handler with compute-fingerprints will compute and send fingerprints and mw-validate-policy will ensure configuration is in a good state
(mw-validate-policy handler)
middleware to validate an edn deps policy all configurations with a policy=manualConfiguration should have a dependency which is an application/json map all configurations with other policies use a dependency which is an array of strings
middleware to validate an edn deps policy all configurations with a policy=manualConfiguration should have a dependency which is an application/json map all configurations with other policies use a dependency which is an array of strings
(off-target? fingerprint target data->version)
true if fingerprints have same name but different sha although if both versions are semver compliant then the fingerprint must also be semantically earlier than the target. If not, it's considered on target
true if fingerprints have same name but different sha although if both versions are semver compliant then the fingerprint must also be semantically earlier than the target. If not, it's considered on target
(set-up-target-configuration handler)
middleware to construct a manualConfiguration from a dependency configuration containing a '[lib version]' string
middleware to construct a manualConfiguration from a dependency configuration containing a '[lib version]' string
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close