Skip to content
This repository has been archived by the owner on Jul 26, 2022. It is now read-only.

isBinary field does not work with the property field in Azure backend #494

Closed
SayakMukhopadhyay opened this issue Sep 25, 2020 · 2 comments
Closed

isBinary field does not work with the property field in Azure backend #494

SayakMukhopadhyay opened this issue Sep 25, 2020 · 2 comments

Comments

@SayakMukhopadhyay
Copy link

According to the PR at #311, the isBinary field doesn't work with property field for Azure backend. I have a idea to solve this and I am creating this issue to track it.
@SayakMukhopadhyay
Copy link
Author

Essentially I am thinking of an Azure specific option propertyAzure that will be handled by the Azure backend only and won't trip the JSON.parse in the kv backend. This would help the Azure backend have the same compatibility options that is present without the isBinary field. Let me know how this sounds.

@SayakMukhopadhyay SayakMukhopadhyay mentioned this issue Sep 25, 2020
Closed
@Flydiverny
Copy link
Member

See #495

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@Flydiverny @SayakMukhopadhyay