You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Escaping CSV values was discussed in #243 however the resolution in the end was to use \ for escaping commas in CSV files.
This causes an issue when trying to share policies between different versions of Casbin (e.g. Node-Casbin and jCasbin) which use double quotation marks to format values. This is the preferred technique described in RFC4180.
Is there any reason not to switch to the method of escaping CSV values described in RFC4180?
The text was updated successfully, but these errors were encountered:
Escaping CSV values was discussed in #243 however the resolution in the end was to use
\
for escaping commas in CSV files.This causes an issue when trying to share policies between different versions of Casbin (e.g. Node-Casbin and jCasbin) which use double quotation marks to format values. This is the preferred technique described in RFC4180.
Is there any reason not to switch to the method of escaping CSV values described in RFC4180?
The text was updated successfully, but these errors were encountered: