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
{{ message }}
This repository has been archived by the owner on Dec 5, 2022. It is now read-only.
readme.md states "Other attributes are allowed and will be passed as well to relevant functions (eg. filterRequestHeaders, filterResponseHeaders, etc.)", and we do rely on this.
After quite some time we wanted to update tailor and I ran into this bug: fragment.js:26 const getAttributes = (tag, context) =>
changed in commitId d05e816 to improve performance. Thus, now not assigning custom attributes.
Is it okay to go back to "old" behaviour?
Regards
The text was updated successfully, but these errors were encountered:
readme.md states "Other attributes are allowed and will be passed as well to relevant functions (eg. filterRequestHeaders, filterResponseHeaders, etc.)", and we do rely on this.
After quite some time we wanted to update tailor and I ran into this bug:
fragment.js:26 const getAttributes = (tag, context) =>
changed in commitId d05e816 to improve performance. Thus, now not assigning custom attributes.
Is it okay to go back to "old" behaviour?
Regards
The text was updated successfully, but these errors were encountered: