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
log-request! and log-response! are parsing the sensitive keys to send into remove-omissions even though remove-omissions repeats this actions. That means what reaches remove-omissions is nil.
The second bug is that the config passed into new-parser is never actually put into the env. So {:keys [config] :as env} will always get nil as the config.
The text was updated successfully, but these errors were encountered:
To be honest, I'd rather just delete that whole mess than fix it. Be better for the user to just add their own plugin to accomplish it, which is the solution I'd suggest to you.
remove-omissions
does not actually remove sensitive keys because of 2 bugs in its implementation.First, look at what gets passed in:
log-request!
andlog-response!
are parsing the sensitive keys to send intoremove-omissions
even thoughremove-omissions
repeats this actions. That means what reachesremove-omissions
isnil
.The second bug is that the config passed into
new-parser
is never actually put into the env. So{:keys [config] :as env}
will always getnil
as the config.The text was updated successfully, but these errors were encountered: