If the service catalog fails to initialize for whatever reason, e.g. network failure, the consuming application doesn't know
by making the following changes
Added a new attribute on the services called initFailed which is set if the catalog fails to init in the on webex ready handler. Consuming applications can either check webex.internal.services.initFailed directly or can listen for the change:initFailed event to spot when this occurs.
Change Type
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update
[ ] Tooling change
[ ] Internal code refactor
The following scenarios where tested
< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >
COMPLETES #< INSERT LINK TO ISSUE >
This pull request addresses
If the service catalog fails to initialize for whatever reason, e.g. network failure, the consuming application doesn't know
by making the following changes
Added a new attribute on the services called initFailed which is set if the catalog fails to init in the on webex ready handler. Consuming applications can either check webex.internal.services.initFailed directly or can listen for the change:initFailed event to spot when this occurs.
Change Type
The following scenarios where tested
< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >
I certified that
[ ] I have read and followed contributing guidelines
[ ] I discussed changes with code owners prior to submitting this pull request
[ ] I have not skipped any automated checks
[ ] All existing and new tests passed
[ ] I have updated the documentation accordingly
Make sure to have followed the contributing guidelines before submitting.