We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have an app setting with value "2024-05-18T00:00:00.000Z".
Immediately after deployment I noticed that it was showing up as "05/18/2024 00:00:00"
I tried changing it back to "2024-05-18T00:00:00.000Z" in the Portal but that too got converted to "05/18/2024 00:00:00".
Expected behaviour is that the function app should not be changing app settings in any way.
In my case the app setting is being used in a CosmosDB trigger StartFromTime attribute and this requires the ISO format - not this other format.
(I have seen similar unwanted behaviour before with Newtonsoft.Json - not sure if that is also causing the issue here JamesNK/Newtonsoft.Json#862)
The text was updated successfully, but these errors were encountered:
Thanks for reporting please share the all repro steps.Thanks
Sorry, something went wrong.
They are already shared.
Go into the portal.
Change an app setting to "2024-05-18T00:00:00.000Z"
Marvel as it gets silently changed to "05/18/2024 00:00:00"
@fabiocav please comment.Thanks
bhagyshricompany
No branches or pull requests
I have an app setting with value "2024-05-18T00:00:00.000Z".
Immediately after deployment I noticed that it was showing up as "05/18/2024 00:00:00"
I tried changing it back to "2024-05-18T00:00:00.000Z" in the Portal but that too got converted to "05/18/2024 00:00:00".
Expected behaviour is that the function app should not be changing app settings in any way.
In my case the app setting is being used in a CosmosDB trigger StartFromTime attribute and this requires the ISO format - not this other format.
(I have seen similar unwanted behaviour before with Newtonsoft.Json - not sure if that is also causing the issue here JamesNK/Newtonsoft.Json#862)
The text was updated successfully, but these errors were encountered: