[Alarm] Don't raise an error when an alarm without TYPE is found 06/261406/1 accepted/tizen/unified/20210719.025303 submit/tizen/20210716.123403
authorPawel Wasowski <p.wasowski2@samsung.com>
Thu, 15 Jul 2021 13:03:15 +0000 (15:03 +0200)
committerPawel Wasowski <p.wasowski2@samsung.com>
Fri, 16 Jul 2021 09:52:54 +0000 (09:52 +0000)
commit5e990c353179b51279253cb56994d83127829798
tree2d00158490525ec3a68a9b00d6025612dcffadef
parent07171f83626b19c5a62f95a4f9d31690c2785bd3
[Alarm] Don't raise an error when an alarm without TYPE is found

tizen.alarm.get() and tizen.alarm.getAll() used to fail when alarms
without "TYPE" property in related app_control existed.
This commit returns such alarms as JS Alarm objects.

[Verification] tct-alarm-tizen-tests (auto): 100 %

I've tested in Chrome DevTools debugger, that when an alarm without
"type" property comes to JS, a valid "Alarm" object is created
(I don't provide any test code snippet, because it required stopping
app in the debugger).

Change-Id: I4b5bcea75509f454bd17b787c080417849720f5a
Signed-off-by: Pawel Wasowski <p.wasowski2@samsung.com>
src/alarm/alarm_api.js
src/alarm/alarm_manager.cc