Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom Date Time Format - stripping leading zero from day value #367

Closed
cmjchrisjones opened this issue May 30, 2019 · 6 comments
Closed

Comments

@cmjchrisjones
Copy link

  • VSCode Version: 1.33.1 (User Setup)
  • OS Version: Win 10 Enterprise
  • REST Client Version: 0.21.3

Background

@connelhooley recently made a change to resolve #325 which allows us to use a custom date format as well as specifying a dynamic date in PR #361, although, again this is specific to just our use case, I noticed that when doing "{{$datetime 'YYYY-MM-DD' 5 d}}" today (30th May, 5 days from now being 4th June), it isn't including the leading 0 for the day, we are getting the following response from our internal API

"message": "Supplied value could not be accepted. Supplied date '2019-06-4' is invalid, ensure to supply in yyyy-MM-dd format."

@Huachao
Copy link
Owner

Huachao commented May 31, 2019

@cmjchrisjones nice catch, I have fixed the issue and will publish it in next release.

@Huachao Huachao closed this as completed May 31, 2019
@cmjchrisjones
Copy link
Author

Thanks, looking forward to the next release 👍

@MrXhh
Copy link

MrXhh commented Jun 4, 2019

Replace "%USERNAME%.vscode\extensions\humao.rest-client-0.21.3\dist\extension.js" with the file in "extension.zip" if you need it urgently.
My plugin version is: 0.21.3

extension.zip

@connelhooley
Copy link
Contributor

Is there any update on when this will be released? I'd rather not get our entire team to download the zip and manually update the extension if possible.

Thanks

@Huachao
Copy link
Owner

Huachao commented Jul 29, 2019

@connelhooley it should be released in this week 😄

@Huachao
Copy link
Owner

Huachao commented Jul 31, 2019

@connelhooley @cmjchrisjones @MrXhh this fix has been published in latest version 0.22.0, you can try it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants