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
@nutterb, just a heads up. I've had two recent issues created that ended up being caused by curly quotes in the data dictionary. The solution involved being more explicit with the text & encoding passed to httr::content().
I know you use httr::POST() instead (and I like that there are two approaches available to the public) and I don't know if there's an analog for your approach. Maybe httr::POST() avoids it entirely.
If you start seeing things like these two REDCapR issues, it may be worth investigating. It may address redcapAPI's nutterb/redcapAPI#126 & nutterb/redcapAPI#129?
I'll keep an eye out for it, but I may be able to avoid the problem. redcapAPI has an option to use iconv to obliterate non ASCII characters. It's a little heavy handed, but made for a simple and quick solution
@nutterb, just a heads up. I've had two recent issues created that ended up being caused by curly quotes in the data dictionary. The solution involved being more explicit with the text & encoding passed to
httr::content()
.I know you use
httr::POST()
instead (and I like that there are two approaches available to the public) and I don't know if there's an analog for your approach. Maybehttr::POST()
avoids it entirely.If you start seeing things like these two REDCapR issues, it may be worth investigating. It may address redcapAPI's nutterb/redcapAPI#126 & nutterb/redcapAPI#129?
The text was updated successfully, but these errors were encountered: