poorejc commented on pull request #64: URL: https://github.com/apache/incubator-flagon-useralejs/pull/64#issuecomment-802356672
I will note that I have observed some users actually build their own event handlers and fully customize their logs—I didn’t advocate this, but that’s why I modified packageLog and built packageCustomLog—to help enforce data schema consistency even among users who insist on a “tag manager” sort of feel. Not intended use, but not insane. I do agree that those examples might make it confusing re what UserALE does natively. I’ll pass on another example tonight I built for handling an event that we actually don’t listen for (and probably never will add to ./src/attachHandlers. Joshua Poore > On Mar 18, 2021, at 5:14 PM, Rob ***@***.***> wrote: > > > Gotcha, thanks for the thorough explanation! Understood that the Userale map/filter functions operate on the logging pipeline and they operate just like their JS array API counterparts. In the example code above, what is the purpose of adding the event listener? (noting that the snippet was originally taken from examples/index.js) > > as @poorejc mentioned, it is probably just an artifact of quickly writing examples. the only examples i'm familiar with are the first two on the main README.md examples section. it is my fault for not having made a larger body of examples to pull from, as the map/filter/packageCustomLog API should be flexible enough to handle the vast majority of use cases, and it should be possible to do so without writing hacks. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or unsubscribe. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
