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

Package Loading Analytics #11366

Merged
merged 1 commit into from
Jan 4, 2021
Merged

Package Loading Analytics #11366

merged 1 commit into from
Jan 4, 2021

Conversation

QilongTang
Copy link
Contributor

@QilongTang QilongTang commented Dec 16, 2020

Please Note:

  1. Before submitting the PR, please review How to Contribute to Dynamo
  2. Dynamo Team will meet 1x a month to review PRs found on Github (Issues will be handled separately)
  3. PRs will be reviewed from oldest to newest
  4. If a reviewed PR requires changes by the owner, the owner of the PR has 30 days to respond. If the PR has seen no activity by the next session, it will be either closed by the team or depending on its utility will be taken over by someone on the team
  5. PRs should use either Dynamo's default PR template or one of these other template options in order to be considered for review.
  6. PRs that do not have one of the Dynamo PR templates completely filled out with all declarations satisfied will not be reviewed by the Dynamo team.
  7. PRs made to the DynamoRevit repo will need to be cherry-picked into all the DynamoRevit Release branches that Dynamo supports. Contributors will be responsible for cherry-picking their reviewed commits to the other branches after a LGTM label is added to the PR.

Purpose

Package loading analytics including

  • loading packages
  • uninstall packages

See linked PR: https://git.autodesk.com/Dynamo/Analytics.NET/pull/27

Not covered

  • install packages (tracked by back end)
  • up vote/ down vote packages (tracked by back end)

Declarations

Check these if you believe they are true

  • The codebase is in a better state after this PR
  • Is documented according to the standards
  • The level of testing this PR includes is appropriate
  • User facing strings, if any, are extracted into *.resx files
  • All tests pass using the self-service CI.
  • Snapshot of UI changes, if any.
  • Changes to the API follow Semantic Versioning and are documented in the API Changes document.
  • This PR modifies some build requirements and the readme is updated

Reviewers

@zeusongit

FYIs

(FILL ME IN, Optional) Names of anyone else you wish to be notified of

@QilongTang
Copy link
Contributor Author

Looking at more areas of package loading missing aspects from analytics

@QilongTang QilongTang marked this pull request as ready for review January 4, 2021 19:07
@QilongTang QilongTang requested a review from zeusongit January 4, 2021 19:23
@QilongTang QilongTang merged commit d1195be into master Jan 4, 2021
@QilongTang QilongTang deleted the PackageLoadingAnalytics branch January 4, 2021 20:13
QilongTang added a commit that referenced this pull request Jan 27, 2021
@QilongTang QilongTang mentioned this pull request Jan 27, 2021
8 tasks
QilongTang added a commit that referenced this pull request Jan 28, 2021
* Dock and Undock view extension with Dynamic extension ID as edge case (#11394)

* Initial Commit with settings null check

* Add unit test

* Add view extension loading warning

* Update message

* Initial Commit (#11366)

* Do not aggregate node execution analytics anymore (#11356)

* Do not aggregate node execution analytics anymore

* Update to use new event combo

* Update Comments

* Make IntegerSlider the only AKA for migration (#11360)

There were two classes that were declaring an 'AlsoKnownAs' attribute
for 'DSCoreNodesUI.Input.IntegerSlider' in 'CoreNodeModels.Input':
'IntegerSlider' and 'IntegerSlider64Bit'. While the latter obsoletes
the former, it is not possible to migrate to it from XML, so only 
'IntegerSlider' should continue declaring an 'AlsoKnownAs' attribute.
Note that currently both classes are trying to be registered, which
results in only one of them being registered but not really making any
guarantees of which one it is. This also generates an exception catched
internally but shown in the console.

* Revised icons for AnyTrue and AnyFalse nodes (#11361)

* Implement ToString for DS Dictionary (#11358)

This is done to provide meaningful output when a dictionary is provided
to nodes like 'String from Array' and 'String from Object'. These nodes
call built-in DS functions that end up calling ToString on the
dictionary, which until now used the default implementation inherited
from Object which just returned the class name.

Co-authored-by: Martin Misol Monzo <[email protected]>
Co-authored-by: Laurence Elsdon <[email protected]>
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