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

chore: Remove duplicated ChannelDeletionTable #32114

Merged
merged 2 commits into from
Apr 3, 2024

Conversation

dougfabris
Copy link
Member

@dougfabris dougfabris commented Apr 2, 2024

Proposed changes (including videos or screenshots)

Remove duplicated code

Issue(s)

Steps to test or reproduce

Further comments

CORE-284

Copy link

changeset-bot bot commented Apr 2, 2024

⚠️ No Changeset found

Latest commit: c5f80f5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@dougfabris dougfabris added this to the 7.0 milestone Apr 2, 2024
Copy link

codecov bot commented Apr 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 52.37%. Comparing base (d0862cb) to head (c5f80f5).

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop   #32114      +/-   ##
===========================================
- Coverage    54.40%   52.37%   -2.04%     
===========================================
  Files         2255     2180      -75     
  Lines        49973    48818    -1155     
  Branches     10167     9968     -199     
===========================================
- Hits         27188    25568    -1620     
- Misses       20315    20956     +641     
+ Partials      2470     2294     -176     
Flag Coverage Δ
e2e 48.97% <100.00%> (-4.00%) ⬇️
e2e-api 40.14% <ø> (+0.03%) ⬆️
unit 75.39% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@dougfabris dougfabris force-pushed the chore/removeChannelDeletionTable branch from 6906bc4 to eb04c32 Compare April 3, 2024 13:52
Copy link
Contributor

dionisio-bot bot commented Apr 3, 2024

Looks like this PR is not ready to merge, because of the following issues:

  • This PR is not mergeable
    Please fix the issues and try again
    If you have any trouble, please check the PR guidelines

@dougfabris dougfabris added the stat: QA assured Means it has been tested and approved by a company insider label Apr 3, 2024
@dionisio-bot dionisio-bot bot added the stat: ready to merge PR tested and approved waiting for merge label Apr 3, 2024
@dougfabris dougfabris marked this pull request as ready for review April 3, 2024 14:39
@dougfabris dougfabris requested a review from a team as a code owner April 3, 2024 14:39
@dionisio-bot dionisio-bot bot added stat: ready to merge PR tested and approved waiting for merge and removed stat: ready to merge PR tested and approved waiting for merge labels Apr 3, 2024
@kodiakhq kodiakhq bot merged commit 0fcf1f0 into develop Apr 3, 2024
44 of 45 checks passed
@kodiakhq kodiakhq bot deleted the chore/removeChannelDeletionTable branch April 3, 2024 16:01
gabriellsh added a commit that referenced this pull request Apr 4, 2024
* develop: (71 commits)
  fix: search room not reactive after room name changes (#32123)
  test: fix `should edit name of targetChannel` flaky test (#32121)
  fix: UI allowing to mark room as favorite despite room was not a `default` room (#32063)
  chore: Remove duplicated `ChannelDeletionTable` (#32114)
  test(livechat): fix Department flaky test (#32102)
  test(livechat): File upload settings (#32060)
  test: contact center after hook calling wrong endpoint (#32094)
  fix(livechat): registering guest multiple times cause message loss (#32069)
  test: allow csp for livechat tests (#32116)
  chore: Move portals to the portals folder (#32090)
  test: `InitialData.insertAdminUserFromEnv` (#32066)
  fix: `CSP` error right after `setInlineScriptsAllowed` (#32108)
  chore: Create/Edit room consistency (#31960)
  chore: Remove references to EE code from the app events (#31926)
  test(Livechat): Clean up after registerGuest() test (#32092)
  test: make presence api tests fully independent (#31782)
  test: make roles fully independent (#31783)
  chore: bump version to 7.0.0-develop
  test: make login api tests fully independent (#31786)
  fix!: api login should not suggest which credential is wrong (#32086)
  ...
gabriellsh added a commit that referenced this pull request Apr 4, 2024
* origin:
  refactor: `TeamsChannels` to typescript (#32109)
  fix: search room not reactive after room name changes (#32123)
  test: fix `should edit name of targetChannel` flaky test (#32121)
  fix: UI allowing to mark room as favorite despite room was not a `default` room (#32063)
  chore: Remove duplicated `ChannelDeletionTable` (#32114)
  test(livechat): fix Department flaky test (#32102)
  test(livechat): File upload settings (#32060)
  test: contact center after hook calling wrong endpoint (#32094)
  fix(livechat): registering guest multiple times cause message loss (#32069)
  test: allow csp for livechat tests (#32116)
  chore: Move portals to the portals folder (#32090)
  test: `InitialData.insertAdminUserFromEnv` (#32066)
  fix: `CSP` error right after `setInlineScriptsAllowed` (#32108)
@ggazzo ggazzo modified the milestones: 7.0, 6.8 Apr 9, 2024
@dionisio-bot dionisio-bot bot removed the stat: ready to merge PR tested and approved waiting for merge label Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stat: QA assured Means it has been tested and approved by a company insider
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants