Skip to content

Validate performance metrics and attributes before storing them #1917

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

Merged
merged 9 commits into from
Aug 20, 2019

Conversation

kim-f
Copy link
Contributor

@kim-f kim-f commented Jun 26, 2019

No description provided.

@kim-f kim-f requested a review from alikn June 26, 2019 13:05
@kim-f kim-f requested a review from zijianjoy as a code owner June 26, 2019 13:05
@kim-f kim-f force-pushed the performance-sdk-validation branch from 2df8458 to 0901f8a Compare August 6, 2019 17:50
@kim-f kim-f force-pushed the performance-sdk-validation branch from 0901f8a to 045cbdf Compare August 20, 2019 15:44
@kim-f kim-f merged commit 4d0d246 into master Aug 20, 2019
});

it('returns false when name starts with a reserved prefix', () => {
expect(isValidCustomMetricName('_invalidMetricName')).to.be.false;
Copy link

Choose a reason for hiding this comment

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

@kim-f Hello, I have noticed that i'm getting an uncaught exception for _fp as defined in

export const FIRST_PAINT_COUNTER_NAME = '_fp';

can this be updated to ignore the already defined constants?

@firebase firebase locked and limited conversation to collaborators Oct 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants