openlmis-ref-distro

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Bump apache-superset from 0.36.0 to 0.37.2 in /reporting/superset

Bumps [apache-superset](https://github.com/apache/superset) from 0.36.0 to 0.37.2.

- [Release notes](https://github.com/apache/superset/releases)

- [Changelog](https://github.com/apache/superset/blob/master/CHANGELOG.md)

- [Commits](https://github.com/apache/superset/compare/0.36.0...0.37.2)

Signed-off-by: dependabot[bot] <support@github.com>

OLMIS-7253: Added slugs to superset dashboards

OLMIS-7253: Added facilities materialized view
OLMIS-7253: Added facilities materialized view
OLMIS-7254: Time range changed for Stock Filter and District Stockout Rates over Time

OLMIS-7253: Changed column names in Administrative report

OLMIS-7253: Changed column name in facilities materialized view

OLMIS-7253: Added facilities materialized view

    • -0
    • +1
    /reporting/cron/periodic/15min/refresh-mv
OLMIS-7249: Temporarily enabled registration of Debezium connectors
OLMIS-7249: Temporarily enabled registration of Debezium connectors
OLMIS-7249: Temporarily enabled registration of Debezium connectors

OLMIS-7219: Updated POST /order and /orders/batch to return existing orders if already created
OLMIS-7219: Updated POST /order and /orders/batch to return existing orders if already created
OLMIS-7219: Updated fulfillment version to 9.0.0-SNAPSHOT

NullPointer is thrown in that case.

NullPointer is thrown in that case.

Let's not change behavior for this endpoint

Let's not change behavior for this endpoint

there's no "requisition" concept in fulfillment - let's stick to external id

there's no "requisition" concept in fulfillment - let's stick to external id

9.0.0 - major version needs to be updated in case of breaking changes

9.0.0 - major version needs to be updated in case of breaking changes

Actually, let's not change this behavior for POST /orders - it should still return 400 if the order already exists

Actually, let's not change this behavior for POST /orders - it should still return 400 if the order already exists

Do we need this check? What happens if I try to find by null value?

Do we need this check? What happens if I try to find by null value?

OLMIS-7179: Adjusted scripts after renaming apache/incubator-superset to apache/superset
OLMIS-7179: Adjusted scripts after renaming apache/incubator-superset to apache/superset
OLMIS-7179: Adjusted scripts after renaming apache/incubator-superset to apache/superset

Added v3.10 release notes.

    • binary
    /docs/source/releases/UI-Performance-3.10.png
    • -0
    • +237
    /docs/source/releases/openlmis-ref-distro-v3.10.0.rst
OLMIS-7177: Updated fulfillment and stock management versions