Skip to content

Conversation

codecapitano
Copy link
Collaborator

@codecapitano codecapitano commented Sep 29, 2025

Why

Hackathon:

User interaction instrumentation:
Tracks click, change and submit events.

We track events during the capture phase so we shouldn't cover mostly all events.

Event payload is:

 faro.api.pushEvent(
        `userInteraction-${eventType}`,
        {
          event: eventType,
          element: elementType,
          identifier: elementIdentifier,
        },
        undefined,
        { skipDedupe: true }
      );
    }

What

Links

Checklist

  • Tests added
  • Changelog updated
  • Documentation updated

@codecapitano codecapitano self-assigned this Sep 29, 2025
@codecapitano codecapitano added the feature Request a new feature label Sep 29, 2025

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

Copy link

github-actions bot commented Oct 2, 2025

😢 zizmor failed with exit code 14.

Expand for full output
error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
  --> ./.github/workflows/release.yml:22:9
   |
 3 | / on:
 4 | |   push:
 5 | |     tags:
 6 | |       - '*'
   | |___________- generally used when publishing artifacts generated at runtime
...
22 |           uses: actions/setup-node@v5
   |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^ cache enabled by default here
   |
   = note: audit confidence → Low

error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
  --> ./.github/workflows/release.yml:71:9
   |
 3 | / on:
 4 | |   push:
 5 | |     tags:
 6 | |       - '*'
   | |___________- generally used when publishing artifacts generated at runtime
...
71 |           uses: actions/setup-node@v5
   |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^ cache enabled by default here
   |
   = note: audit confidence → Low

error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
   --> ./.github/workflows/release.yml:110:9
    |
  3 | / on:
  4 | |   push:
  5 | |     tags:
  6 | |       - '*'
    | |___________- generally used when publishing artifacts generated at runtime
...
110 |           uses: actions/setup-node@v5
    |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^ cache enabled by default here
    |
    = note: audit confidence → Low

19 findings (16 suppressed): 0 informational, 0 low, 0 medium, 3 high

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature Request a new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant