CHANGELOG.md

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Please change "non versioned" to "nonversioned" or "non-versioned".

Please change "non versioned" to "nonversioned" or "non-versioned".

not the latest version, probably

not the latest version, probably

Please change the description to not contain "2" at the end.

Please change the description to not contain "2" at the end.

Do we have some tests for those functions?

Do we have some tests for those functions?

OLMIS-6487: Added functions to get latest and versioned documents from local database
OLMIS-6487: Added functions to get latest and versioned documents from local database
OLMIS-6487: Added implementation for get and getAll functions in OpenlmisCacheResource

  1. … 5 more files in changeset.
OLMIS-6222: Fixed pagination
OLMIS-6222: Fixed pagination
OLMIS-6222: Added paginationId attribute to pagination

  1. … 5 more files in changeset.
Revert "OLMIS-6222: Added paginationId attribute to pagination"

This reverts commit 05e09a1feda4b94024c2be546c75bffc1adc4cb1.

  1. … 5 more files in changeset.
OLMIS-6222: Added paginationId attribute to pagination

  1. … 5 more files in changeset.
OLMIS-6441: Added directive positive-decimal
OLMIS-6441: Added directive positive-decimal
OLMIS-6441: Added directive positive-decimal

  1. … 1 more file in changeset.
OLMIS-6442: Added withConfirm function to FunctionDecorator class

  1. … 2 more files in changeset.
Missing unit tests.

Missing unit tests.

MIssing JSDocs.

MIssing JSDocs.

Nevermind.

Nevermind.

Is this required if we only have single accessRight?

Is this required if we only have single accessRight?

Missing JSDoc.

Missing JSDoc.

FTAP or facility type approved products

FTAP or facility type approved products

Could we add a "withConfirm" method to the FunctionDecorator?

Could we add a "withConfirm" method to the FunctionDecorator?

Any reason why this is in a separate file? Are we reusing it somewhere?

Any reason why this is in a separate file? Are we reusing it somewhere?

Could we make the save function accept an object and use .extend instead of updating the object by hand? This would be something like: .extend({}, result.content[0], vm.facilityTypeApprovedProduct)

Could we make the save function accept an object and use .extend instead of updating the object by hand? This would be something like:
.extend({}, result.content[0], vm.facilityTypeApprovedProduct)

This could be a call to the goToFtapsList instead.

This could be a call to the goToFtapsList instead.