hezyin opened a new issue, #5097:
URL: https://github.com/apache/incubator-devlake/issues/5097

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   **Version: v0.17.0-beta3**
   
   This issue probably only requires some text update on the Config-UI side. 
Note how Config-UI suggests that start_time is optional in the following 
screenshot:
   
   ![Screen Shot 2023-05-04 at 11 08 34 
AM](https://user-images.githubusercontent.com/2908155/236299328-370f7c85-cc97-42c8-96ab-91627f0af928.png)
   
   But if I got the following error when I didn't pass start_time and I was 
able to succeed after passing start_time:
   ![Screen Shot 2023-05-04 at 11 07 30 
AM](https://user-images.githubusercontent.com/2908155/236299708-b3c67f19-323b-4a53-bb94-6442b391b76b.png)
   
   When updating the curl command template, could you please also format it 
like below and use single quotation marks outside the curly braces so that we 
don't need to escape double quotation marks inside the payload?
   
   ![Screen Shot 2023-05-04 at 11 08 37 
AM](https://user-images.githubusercontent.com/2908155/236300027-050d9f1c-3796-43a6-9a4d-796c98f7f58d.png)
   
   (this is from webhook plugin doc page: 
https://devlake.apache.org/docs/next/Plugins/webhook)
   
   
   
   ### What do you expect to happen
   
   See above
   
   ### How to reproduce
   
   See above
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   main
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to