zf

zenflows testing
git clone https://s.sonu.ch/~srfsh/zf.git
Log | Files | Refs | Submodules | README | LICENSE

CHANGELOG.md (3919B)


      1 # Changelog
      2 
      3 All notable changes to this project will be documented in this file.
      4 
      5 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
      6 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
      7 
      8 ## [1.1.0](https://github.com/elixir-telemetry/telemetry/tree/v1.1.0)
      9 
     10 ### Added
     11 
     12 - Added `monotonic_time` measurement to all span events. (#92)
     13 - Added a `[telemetry, handler, failure]` event emitted when any handler fails and is detached. (#98)
     14 - Added a `mix.exs` file, lowering the memory footprint of compilation in Elixir projects. (#103)
     15 
     16 ## [1.0.0](https://github.com/elixir-telemetry/telemetry/tree/v1.0.0)
     17 
     18 There are no changes in the 1.0.0 release - it marks the stability of the API.
     19 
     20 ## [0.4.3](https://github.com/elixir-telemetry/telemetry/tree/v0.4.3)
     21 
     22 This release improves the `telemetry:span/3` function by adding the `telemetry_span_context` metadata
     23 to all span events. The new metadata enables correlating span events that belong to the same span.
     24 
     25 ### Added
     26 
     27 - Added `telemetry_span_context` metadata to all events emitted by `telemetry:span/3`.
     28 
     29 ## [0.4.2](https://github.com/elixir-telemetry/telemetry/tree/v0.4.2)
     30 
     31 ### Added
     32 
     33 - Added the `telemetry:span/3` function.
     34 
     35 ## [0.4.1](https://github.com/elixir-telemetry/telemetry/tree/v0.4.1)
     36 
     37 Apart from the code changes listed below, this release includes a few improvements
     38 to the documentation.
     39 
     40 ### Changed
     41 
     42 - Calls to `execute/3` when `telemetry` application is not started no longer cause an error.
     43 
     44 ## [0.4.0](https://github.com/elixir-telemetry/telemetry/tree/v0.4.0)
     45 
     46 A single event value has been replaced by a map of measurements. Now it is up to the consumer of the
     47 event to decide what part of the payload is important. This is useful in cases where event indicates
     48 that a thing happened but there are many properties describing it. For example, a database query
     49 event may include total time, decode time, wait time and other measurements.
     50 
     51 ### Changed
     52 
     53 - `execute/3` now accepts a map of measurements instead of event value
     54 
     55 ### Deprecated
     56 
     57 - `:telemetry.execute/3` with an event value in favour of `:telemetry.execute/3` with a map of
     58   measurements. If the event value is provided, it is put in a map under a `:value` key and provided
     59   as measurements to a handler function.
     60 
     61 ## [0.3.0](https://github.com/elixir-telemetry/telemetry/tree/v0.3.0)
     62 
     63 This release marks the conversion from Elixir to Erlang. This is a breaking change, but the benefits
     64 largely surpass the drawbacks - Telemetry core can now be used by all projects running on the BEAM,
     65 regardless of the language they're written in.
     66 
     67 ### Added
     68 
     69 - Added `:telemetry.handler/0`, `:telemetry.handler_function/0` and `:telemetry.handler_config/0`
     70   types.
     71 
     72 ### Changed
     73 
     74 - The library has been rewritten to Erlang. In Elixir, `:telemetry` module has to be used in place
     75   of `Telemetry`. In Erlang, `telemetry` module has to be used in place of `'Elixir.Telemetry'`;
     76 - `:telemetry.list_handlers/1` returns a list of maps (of type `:telemetry.handler/0`) instead of
     77   a list of tuples;
     78 - `:telemetry.attach/4` and `:telemetry.attach_many/4` replaced the 5-arity versions and now accept
     79   an anonymous function for the handler function instead of a module and function name.
     80 
     81 ### Removed
     82 
     83 - Removed `:telemetry.attach/5` and `:telemetry.attach_many/5` - 4-arity versions need to be used
     84   now instead.
     85 
     86 ## [0.2.0](https://github.com/elixir-telemetry/telemetry/tree/v0.2.0)
     87 
     88 The main point of this release is to mark base Telemetry API as stable, so that other libraries can
     89 rely on it without worrying about backwards compatibility.
     90 
     91 ### Removed
     92 
     93 - Removed `Telemetry.attach/4` and `Telemetry.attach_many/4` - the handler config is now required.
     94 
     95 ### Fixed
     96 
     97 - Fixed type specs which were producing Dialyzer errors.
     98 
     99 ## [0.1.0](https://github.com/elixir-telemetry/telemetry/tree/v0.1.0)
    100 
    101 First release of Telemetry library.