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

[RHOAIENG-6314] Add tracking for new Homepage. #2781

Merged
merged 1 commit into from
May 21, 2024

Conversation

pilhuhn
Copy link
Contributor

@pilhuhn pilhuhn commented May 7, 2024

Description

This adds tracking for the new home page. As part of this, trackign of the new project
button has moved from the NewProjectButton to the ManageProjectsModal.
[RHOAIENG-6314]

How Has This Been Tested?

By hand and by watching the browser console.

Test Impact

Functionality of the UI has not changed.

Request review criteria:

Self checklist (all need to be checked):

  • The developer has manually tested the changes and verified that the changes work
  • Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

After the PR is posted & before it merges:

  • The developer has tested their solution on a cluster by using the image produced by the PR to main

@openshift-ci openshift-ci bot added the needs-ok-to-test The openshift bot needs to label PRs from non members to avoid strain on the CI label May 7, 2024
Copy link
Contributor

openshift-ci bot commented May 7, 2024

Hi @pilhuhn. Thanks for your PR.

I'm waiting for a opendatahub-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@dgutride
Copy link
Contributor

dgutride commented May 7, 2024

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test The openshift bot needs `ok-to-test` to allow non member PRs to run the tests. and removed needs-ok-to-test The openshift bot needs to label PRs from non members to avoid strain on the CI labels May 7, 2024
@@ -24,11 +22,6 @@ const NewProjectButton: React.FC<NewProjectButtonProps> = ({ closeOnCreate, onPr
<ManageProjectModal
open={open}
onClose={(newProjectName) => {
fireTrackingEvent('NewProject Created', {
Copy link
Member

Choose a reason for hiding this comment

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

Why did you drop this?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is now handled inside the ManageProjectModal at https://github.com/opendatahub-io/odh-dashboard/pull/2781/files#diff-8827454ead4ff8421767576741c1ec341bf780e07671a2c37a34fd2677fbb7caR51 , because the Modal is called from multiple places.

Copy link
Member

Choose a reason for hiding this comment

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

@pilhuhn there are 5 use cases of NewProjectButton -- you point at solving 1. What about the other 4?

Copy link
Member

@andrewballantyne andrewballantyne May 15, 2024

Choose a reason for hiding this comment

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

I only ask because we sound like we are losing overall tracking, to get tracking for the home page

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll have a look in a minute (once the tranisition to the new laptop is kind of finished). Moving the tracking code inside ManagedProjectModal should catch them all. Before there was this button and also the new NewProject link on the new home page.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@andrewballantyne I am not sure I understand your question. The tracking code has moved from NewProjectButton into ManageProjectModal, which is part of the internal implementation of the NewProjectButton.
I did that because the ProjectsSection is using the modal directly and not via NewProjectButton.

Copy link
Member

Choose a reason for hiding this comment

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

I misunderstood it when I briefly was looking at it earlier. Thanks for the clarification.

@andrewballantyne
Copy link
Member

This PR looks good -- just one question (see my message earlier)

Copy link
Contributor

openshift-ci bot commented May 21, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andrewballantyne, jeff-phillips-18

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 1c223b6 into opendatahub-io:main May 21, 2024
6 checks passed
@pilhuhn pilhuhn deleted the home-page-tracking branch October 8, 2024 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm ok-to-test The openshift bot needs `ok-to-test` to allow non member PRs to run the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants