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
The current use case for having the data prefilter before the url parsing prefilter is that it would allow you to create temporary keys for use in the URL prefilter. If the URL prefilter runs first, it removes data and you cannot reuse those keys in the dataMap. However, I'd also like to see greater control over being able to turn off/replace prefilters easily without having to do anything crazy with amplify unsubscribe.
The text was updated successfully, but these errors were encountered:
The current use case for having the data prefilter before the url parsing prefilter is that it would allow you to create temporary keys for use in the URL prefilter. If the URL prefilter runs first, it removes data and you cannot reuse those keys in the dataMap. However, I'd also like to see greater control over being able to turn off/replace prefilters easily without having to do anything crazy with amplify unsubscribe.
The text was updated successfully, but these errors were encountered: