V4Core v3.100.0

🏠 Internal

• RC branch merge

v3.100.0-rc.3

🚀 New Feature

• Added a new option noContentStatuses. This option allows to pass custom status code, array or range of status codes
  which indicate a no-content response. By default, an array [...Range(100, 199), 204, 304] is used, but it may be useful
  to override this value if your backend uses different status codes for no-content responses. core/request

V4Core v4.0.0-alpha.40

🐛 Bug Fix

• Fixed an incorrect import from core/status-codes. core/request/engines/composition

V4Core v3.100.0-rc.2

🐛 Bug Fix

• Fixed an incorrect import from core/status-codes. core/request/engines/composition

V4Core v4.0.0-alpha.39

v4.0.0-alpha.39 (2024-07-01)

🚀 New Feature

• Added a new engine for the request module - compositionEngine. compositionEngine allows you to solve problems
  composition of requests in more complex structures (such as Provider). core/request/engines/composition

V4Core v3.100.0-rc.1

🚀 New Feature

• Added a new engine for the request module - compositionEngine. compositionEngine allows you to solve problems
  composition of requests in more complex structures (such as Provider). core/request/engines/composition

V4Core v4.0.0-alpha.38

🚀 New Feature

• Added a new option noContentStatuses. This option allows to pass custom status code, array or range of status codes
  which indicate a no-content response. By default, an array [...Range(100, 199), 204, 304] is used, but it may be useful
  to override this value if your backend uses different status codes for no-content responses. core/request

V4Core v4.0.0-alpha.37

🐛 Bug Fix

• Fixed an issue with clearing nextTick core/async

V4Core v4.0.0-alpha.36

🐛 Bug Fix

• Fixed an issue where an internal property, blackList, was being written to the target object

V4Core v4.0.0-alpha.35

🐛 Bug Fix

• Added logic that checks whether the passed instance is of the native Headers class or V4Headers.
  To avoid overwriting response header values, we use the append method when handling the native Headers object
  received from the response, while retaining the original practice of setting headers with the set method when
  constructing request headers core/request/headers