[
https://issues.apache.org/jira/browse/FLAGON-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16976305#comment-16976305
]
Joshua Poore commented on FLAGON-470:
-------------------------------------
[~rf]
Generally, you're right, Rob. Users have been asking for us to expose
PackageLog as part of the larger API so that they can pass custom events
through it and standardize their custom logs with raw logs. However, packageLog
doesn't allow users to grab the event itself and pull attributes from it. For
users that want to use packageLog along with the custom Log function, they want
us to expose event so that they can extract its properties.
Example: with event, they can grab e.target and other attributes like
'innerHTML'. Make sense?
> Expose event object in Package Log to allow users to add, extract properties
> to events
> --------------------------------------------------------------------------------------
>
> Key: FLAGON-470
> URL: https://issues.apache.org/jira/browse/FLAGON-470
> Project: Flagon
> Issue Type: Task
> Components: UserALE.js
> Affects Versions: UserALE.js 2.1.0
> Reporter: Joshua Poore
> Assignee: Joshua Poore
> Priority: Major
> Fix For: UserALE.js 2.1.0
>
>
> Expose event object in PackageLog to allow users to add, extract properties
> to events in exported PackageLog object.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
