openlmis-date

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
OLMIS-6456 - Deleted hardcoded date format.

This shouldn't be a hardcoded value.

This shouldn't be a hardcoded value.

OLMIS-6456 Incorrect dates of periods occur in the initiated requisition and in POD
OLMIS-6456 Incorrect dates of periods occur in the initiated requisition and in POD
OLMIS-6456 - Fixed dates filter of periods in the initiated requisition and in POD.

  1. … 1 more file in changeset.
Sure, I added it

Sure, I added it

Could we add a comment under the ticket for QA to test those places when QAing this ticket?

Could we add a comment under the ticket for QA to test those places when QAing this ticket?

tests pass

tests pass

it should fix some other parts like requisitions list

it should fix some other parts like requisitions list

What about some unit tests?

What about some unit tests?

Won't this change break some other parts of the OpenLMIS?

Won't this change break some other parts of the OpenLMIS?

* OLMIS-6301: Removed code where added timezone to string date if not contain timezone definition
* OLMIS-6301: Removed code where added timezone to string date if not contain timezone definition
OLMIS-6330: Testing build

* OLMIS-6301: Removed code where added timezone to string date if not contain timezone definition

  1. … 1 more file in changeset.
Revert "Revert "OLMIS-6261: Refactored unit tests (part 1)""

This reverts commit ce9f844fb5944aeb644055d35d0b201f4eae8110.

    • -14
    • +16
    ./openlmis-datetime.filter.spec.js
  1. … 41 more files in changeset.
Revert "OLMIS-6261: Refactored unit tests (part 1)"

This reverts commit a92390f79fb4dd1c1d8ca9e9823320ff03e014c7.

    • -16
    • +14
    ./openlmis-datetime.filter.spec.js
  1. … 41 more files in changeset.
Could we separate this html fragment of code into a variable just like it is in other tests?

Could we separate this html fragment of code into a variable just like it is in other tests?

Could we separate this html fragment of code into a variable just like it is in other tests?

Could we separate this html fragment of code into a variable just like it is in other tests?

is this change expected?

is this change expected?

is this change expected?

is this change expected?

is this change expected?

is this change expected?

OLMIS-6261: Refactored unit tests (part 1)
OLMIS-6261: Refactored unit tests (part 1)
OLMIS-6261: Refactored unit tests (part 1)

    • -14
    • +16
    ./openlmis-datetime.filter.spec.js
  1. … 41 more files in changeset.