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

Refactor: no need to pass through the ahoy event name dynamically. #18498

Merged
merged 3 commits into from
Sep 28, 2022

Conversation

Ridhwana
Copy link
Contributor

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update

Description

Currently, we pass through the Ahoy Event name but we have specific functions for each event because each one has a unique structure. Hence, we do not need to pass through the name dynamically.

Related Tickets & Documents

QA Instructions, Screenshots, Recordings

UI accessibility concerns?

If your PR includes UI changes, please replace this line with details on how
accessibility is impacted and tested. For more info, check out the
Forem Accessibility Docs.

Added/updated tests?

  • Yes
  • No, and this is why: this is a refactor
  • I need help with writing tests

[Forem core team only] How will this change be communicated?

Will this PR introduce a change that impacts Forem members or creators, the
development process, or any of our internal teams? If so, please note how you
will share this change with the people who need to know about it.

  • I've updated the Developer Docs or
    Storybook (for Crayons components)
  • This PR changes the Forem platform and our documentation needs to be
    updated. I have filled out the
    Changes Requested
    issue template so Community Success can help update the Admin Docs
    appropriately.
  • I've updated the README or added inline documentation
  • I've added an entry to
    CHANGELOG.md
  • I will share this change in a Changelog
    or in a forem.dev post
  • I will share this change internally with the appropriate teams
  • I'm not sure how best to communicate this change and need help
  • This change does not need to be communicated, and this is why not: refactor

[optional] Are there any post deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

alt_text

@Ridhwana Ridhwana requested a review from a team as a code owner September 26, 2022 09:31
@Ridhwana Ridhwana requested review from jaw6 and fdocr and removed request for a team September 26, 2022 09:31
Copy link
Contributor

@fdocr fdocr left a comment

Choose a reason for hiding this comment

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

Makes a lot of sense for it to work this way! 👍🏼

Also: Looked like a flaky cypress test failed, so I just restarted that one Travis job

@Ridhwana Ridhwana merged commit b6b9087 into main Sep 28, 2022
@Ridhwana Ridhwana deleted the Ridhwana/refactor-ca-ahoy-code branch September 28, 2022 17:21
jaw6 added a commit that referenced this pull request Oct 3, 2022
…_tracking_rollup

* origin/main:
  Remove featured_number from articles table (#18514)
  Snackbar error message in comments image upload (#18504)
  Restore DisplayAd search (#18511)
  Update strong_migrations to version 1.3.1 (#18516)
  Refactor: no need to pass through the ahoy event name dynamically. (#18498)
  Remove featured number usage from articles (#18510)
  [ruby] Update sidekiq: 6.5.6 → 6.5.7 (patch) (#18507)
  Update recaptcha to version 5.12.3 (#18506)
  Update octokit to version 5.6.1 (#18505)
  Feed experiment for 09-26-2022 (#18501)
  Update all Yarn dependencies (2022-09-26) (#18497)
TERNOX pushed a commit to TERNOX/forem-bezmir that referenced this pull request Oct 7, 2022
…orem#18498)

* refactor: the name does not need to be passed through dynamically

* refactor: the name does not need to be passed through dynamically

* chore: remove name from the js doc
TERNOX pushed a commit to TERNOX/forem-bezmir that referenced this pull request Jan 5, 2025
…orem#18498)

* refactor: the name does not need to be passed through dynamically

* refactor: the name does not need to be passed through dynamically

* chore: remove name from the js doc
TERNOX pushed a commit to TERNOX/forem-bezmir that referenced this pull request Jan 5, 2025
…orem#18498)

* refactor: the name does not need to be passed through dynamically

* refactor: the name does not need to be passed through dynamically

* chore: remove name from the js doc
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.

3 participants