Closed as not planned
Description
When calling the deployer GitHub action without setting any values for the options
input, the following error message appears: Invalid JSON in options
It doesn't break the deployment, however an error message in a successful deployment log feels weird :) And with no actual problems occurring, I was wondering if the error detection is slightly off.
I'm not familiar with the try-catch logic yet, so I cannot provide and improvement as a PR at this time.
Relevant code snippet:
Lines 116 to 126 in 06aeb29
Readme section:
Lines 26 to 29 in 06aeb29
Upvote & Fund
- We're using Polar.sh so you can upvote and help fund this issue.
- We receive the funding once the issue is completed & confirmed by you.
- Thank you in advance for helping prioritize & fund our backlog.
Metadata
Metadata
Assignees
Labels
No labels