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

Fixes locked workflow toggle in event type settings #8926

Merged
merged 1 commit into from May 16, 2023

Conversation

CarinaWolli
Copy link
Member

What does this PR do?

Fixes that the toggle to disable a workflow on a user event type is locked

This was the bug:
Screenshot 2023-05-16 at 11 50 09

Type of change

  • Bug fix (non-breaking change which fixes an issue)

How should this be tested?

  • Create a user workflow
  • Set it active on a normal user event type
  • Got to the settings of that event type and click the workflows tab
  • See that the toggle of the workflow is not locked and workflow can be disabled

@CarinaWolli CarinaWolli requested a review from a team May 16, 2023 09:54
@vercel
Copy link

vercel bot commented May 16, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
cal ✅ Ready (Inspect) Visit Preview May 16, 2023 9:54am
ui ✅ Ready (Inspect) Visit Preview May 16, 2023 9:54am

@@ -197,7 +197,7 @@ function EventWorkflowsTab(props: Props) {
const dataWf = data.workflows.find((wf) => wf.id === workflowOnEventType.id);
return {
...workflowOnEventType,
readOnly: isChildrenManagedEventType && dataWf?.teamId ? true : dataWf?.readOnly ?? true,
readOnly: isChildrenManagedEventType && dataWf?.teamId ? true : dataWf?.readOnly ?? false,
Copy link
Member Author

Choose a reason for hiding this comment

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

if readOnly is not defined, it shouldn't be read-only

@github-actions
Copy link
Contributor

📦 Next.js Bundle Analysis for @calcom/web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

@deploysentinel
Copy link

Current Playwright Test Results Summary

✅ 98 Passing - ⚠️ 2 Flaky

Run may still be in progress, this comment will be updated as current testing workflow or job completes...

(Last updated on 05/16/2023 10:17:12am UTC)

Run Details

Running Workflow PR Update on Github Actions

Commit: 892a3cd

Started: 05/16/2023 10:06:37am UTC

⚠️ Flakes

📄   apps/web/playwright/booking-seats.e2e.ts • 2 Flakes

Top 1 Common Error Messages

null

2 Test Cases Affected

Test Case Results

Test Case Last 7 days Failures Last 7 days Flakes
Booking with Seats -- new-booker Reschedule for booking with seats -- old-booker Should reschedule booking with seats and if everyone rescheduled it should be deleted
Retry 1Initial Attempt
0% (0) 0 / 334 runs
failed over last 7 days
76.65% (256) 256 / 334 runs
flaked over last 7 days
Booking with Seats -- old-booker Reschedule for booking with seats -- old-booker Should reschedule booking with seats and if everyone rescheduled it should be deleted
Retry 1Initial Attempt
0% (0) 0 / 330 runs
failed over last 7 days
21.82% (72) 72 / 330 runs
flaked over last 7 days

View Detailed Build Results


@hariombalhara hariombalhara added this pull request to the merge queue May 16, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 16, 2023
@CarinaWolli CarinaWolli added this pull request to the merge queue May 16, 2023
Merged via the queue into main with commit 38fb7a3 May 16, 2023
22 checks passed
@CarinaWolli CarinaWolli deleted the fix/locked-workflow-toggle branch May 16, 2023 11:26
sean-brydon pushed a commit that referenced this pull request May 18, 2023
Co-authored-by: CarinaWolli <wollencarina@gmail.com>
@PeerRich PeerRich added the core area: core, team members only label Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core area: core, team members only
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants