Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/conviva/additional error logging #53

Merged
merged 3 commits into from
Oct 15, 2024

Conversation

tvanlaerhoven
Copy link
Member

Extra details for error events, including code, category & stack.
The stack will be truncated by Conviva's SDK, but could still provide valuable information.

Copy link

changeset-bot bot commented Oct 9, 2024

🦋 Changeset detected

Latest commit: 69055eb

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@theoplayer/conviva-connector-web Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

} catch (ignore) {
// Failed to stringify value.
export function flattenErrorObject(error?: THEOplayerError): { [key: string]: string } {
const errorDetails: Record<string, any> = {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now the value is of type any while previously we would always pass it as a string. Is this fine on conviva end or should we stringify the values to be safe?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Jeroen-Veltmans I updated the typings: we always pass a { [key: string]: string } object to Conviva after all undefined or null values are removed from the object.

@tvanlaerhoven tvanlaerhoven merged commit e8480a1 into main Oct 15, 2024
1 check passed
@tvanlaerhoven tvanlaerhoven deleted the feature/conviva/additional_error_logging branch October 15, 2024 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants