referencedata.facility_types.json

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
OLMIS-4871 Rename performance-data folder to demo-data
OLMIS-4871 Rename performance-data folder to demo-data
OLMIS-4871 Move demo data to TestDataInitializer

* Change demo data strategy from JSON to CSV.

* Add more data, not from Mockaroo, but from UAT2.

* Remove old demo-data files.

* Fix sonar bugs.

    • -30
    • +0
    ./referencedata.facility_types.json
  1. … 80 more files in changeset.
Revert demo data back to JSON strategy

Also, change requisition group FP 1 to use regular Monthly processing schedule (to pass requisition contract tests).

    • -0
    • +30
    ./referencedata.facility_types.json
  1. … 71 more files in changeset.
OLMIS-4871 Move demo data to TestDataInitializer

* Change demo data strategy from JSON to CSV.

* Add more data, not from Mockaroo, but from UAT2.

* Remove old demo-data files.

* Fix sonar bugs.

    • -30
    • +0
    ./referencedata.facility_types.json
  1. … 71 more files in changeset.
Revert "OLMIS-4871 Move demo data to TestDataInitializer"

This reverts commit 55caa5a79edd5c686a07cd33ad8b8f93fc350b61.

    • -0
    • +30
    ./referencedata.facility_types.json
  1. … 69 more files in changeset.
OLMIS-4871 Move demo data to TestDataInitializer

* Change demo data strategy from JSON to CSV.

* Add more data, not from Mockaroo, but from UAT2.

* Remove old demo-data files.

    • -30
    • +0
    ./referencedata.facility_types.json
  1. … 69 more files in changeset.
OLMIS-3200 Add vaccine demo data with documentation
OLMIS-3200 Add vaccine demo data with documentation
OLMIS-3200 Add facilities to demo data

Also, geo zones, facility types and supported programs.

    • -0
    • +14
    ./referencedata.facility_types.json
  1. … 3 more files in changeset.
lgtm

lgtm

I still wanted to all those tests to use the same methods, and some of them are creating new multiple types.

I still wanted to all those tests to use the same methods, and some of them are creating new multiple types.

why not generate one in setUp and use field for FacilityType?

why not generate one in setUp and use field for FacilityType?

This is to prevent saving warehouse facility type, because there is one already

This is to prevent saving warehouse facility type, because there is one already

Delete should probably be very rare - and should rather not impact user data.

Delete should probably be very rare - and should rather not impact user data.

Depends - but not sure why we would do this here? What is the impact on facilities? What are we trying to achieve here?

Depends - but not sure why we would do this here? What is the impact on facilities? What are we trying to achieve here?

I'm not sure what is the purpose these lines?

I'm not sure what is the purpose these lines?

Paweł Gesek do you think that is acceptable to delete sth in migrations?

Paweł Gesek do you think that is acceptable to delete sth in migrations?

initial bootstrap shouldn't be changed

initial bootstrap shouldn't be changed

if we extracted private method I think we can use it for these 5 lines as well

if we extracted private method I think we can use it for these 5 lines as well

OLMIS-2492: moved warehouse facility type to initial data

  1. … 3 more files in changeset.
space after code

space after code

OLMIS-2492: added facility type param to facility search endpoint
OLMIS-2492: added facility type param to facility search endpoint