openlmis-ui-components

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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
LGTM. Feel free to apply to other services

LGTM. Feel free to apply to other services

It looks to me like this single line should be enough to not trigger the reference-ui build. Aka. whenever the "when" expression returns false, the stage is not executed. Maybe there's a problem wi...

It looks to me like this single line should be enough to not trigger the reference-ui build. Aka. whenever the "when" expression returns false, the stage is not executed. Maybe there's a problem with this single line only? Looks like we may be referencing the env variable incorrectly.

OLMIS-6330 fixed trigerring reference-ui build
OLMIS-6330 fixed trigerring reference-ui build
OLMIS-6403 Fixed incorrect Start Date and Expiry Date behaviour for system notifications
OLMIS-6403 Fixed incorrect Start Date and Expiry Date behaviour for system notifications
I created the ticket: OLMIS-6412.

I created the ticket: OLMIS-6412.

Do we have a ticket for that?

Do we have a ticket for that?

Perhaps simply openlmisCreationDetails? I could see it reused in places other than messages.

Perhaps simply openlmisCreationDetails? I could see it reused in places other than messages.

Not yet, I would say that maybe this component should be introduced to requisition view in another ticket.

Not yet, I would say that maybe this component should be introduced to requisition view in another ticket.

It is the fix for the problem with this popover being displayed on hover.

It is the fix for the problem with this popover being displayed on hover.

Is this component used by the requisition view?

Is this component used by the requisition view?

Could we make it flexible so that the author always shows fully but the title only occupies as much space as available?

Could we make it flexible so that the author always shows fully but the title only occupies as much space as available?

This should be translateable.

This should be translateable.