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

feat(GST): Implement user timings #329

Merged
merged 3 commits into from
Jan 4, 2019
Merged

Conversation

Marfusios
Copy link
Contributor

  • What kind of change does this PR introduce?
    A new feature into GST provider - user timings, related docs

  • What is the current behavior? Link to open issue?
    User timings API is completely missing in GST

  • What is the new behavior?

@codecov-io
Copy link

codecov-io commented Jan 3, 2019

Codecov Report

Merging #329 into master will decrease coverage by 0.26%.
The diff coverage is 62.5%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #329      +/-   ##
==========================================
- Coverage   79.95%   79.69%   -0.27%     
==========================================
  Files          30       30              
  Lines         898      911      +13     
  Branches      131      133       +2     
==========================================
+ Hits          718      726       +8     
- Misses        110      113       +3     
- Partials       70       72       +2
Impacted Files Coverage Δ
src/lib/providers/gst/gst.ts 76% <62.5%> (-5.09%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e4a6036...356dbc1. Read the comment docs.

!properties.value
) {
console.error(
'Properties name, and value are required to be set.',
Copy link
Collaborator

@scttcper scttcper Jan 3, 2019

Choose a reason for hiding this comment

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

the typescript types already validate these exist right?

I think we can skip developer validation

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's partially true because Typescript is compile-time only so at runtime you will lose all checks (or if somebody doesn't use Typescript compiler at all).
However, it is an Angular library, which has Typescript as the first-class citizen, so we can expect that TS will always be used.

I've removed the checks and left only undefined assert, otherwise, it could throw nasty Uncaught TypeError.

@scttcper scttcper merged commit c484413 into angulartics:master Jan 4, 2019
@scttcper
Copy link
Collaborator

scttcper commented Jan 4, 2019

🎉 This PR is included in version 7.3.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants