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

[CAL-3679] platform: better errors #14977

Closed
PeerRich opened this issue May 10, 2024 · 0 comments · Fixed by #14987
Closed

[CAL-3679] platform: better errors #14977

PeerRich opened this issue May 10, 2024 · 0 comments · Fixed by #14987
Labels
High priority Created by Linear-GitHub Sync 🧹 Improvements Improvements to existing features. Mostly UX/UI platform Anything related to our platform plan
Milestone

Comments

@PeerRich
Copy link
Member

PeerRich commented May 10, 2024

CleanShot 2024-05-10 at 16 00 19@2x

CAL-3679

@PeerRich PeerRich changed the title platform: better errors [CAL-3679] platform: better errors May 10, 2024
@dosubot dosubot bot added platform Anything related to our platform plan 🧹 Improvements Improvements to existing features. Mostly UX/UI labels May 10, 2024
@PeerRich PeerRich added the High priority Created by Linear-GitHub Sync label May 10, 2024
@PeerRich PeerRich added this to the v4.1 milestone May 10, 2024
zomars pushed a commit that referenced this issue May 14, 2024
## What does this PR do?

<!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. -->

- Fixes #14977 

<!-- Please provide a loom video for visual changes to speed up reviews
 Loom Video: https://www.loom.com/
-->

## Mandatory Tasks (DO NOT REMOVE)

- [ ] I have self-reviewed the code (A decent size PR without self-review might be rejected)
- [ ] I have added a Docs issue [here](https://github.com/calcom/docs/issues/new) if this PR makes changes that would require a [documentation change](https://docs.cal.com)
- [ ] I have added or modified automated tests that prove my fix is effective or that my feature works (PRs might be rejected if logical changes are not properly tested)

## How should this be tested?

<!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. Write details that help to start the tests -->

- Are there environment variables that should be set?
- What are the minimal test data to have?
- What is expected (happy path) to have (input and output)?
- Any other important info that could help to test that PR

## Checklist

<!-- Remove bullet points below that don't apply to you -->

- I haven't read the [contributing guide](https://github.com/calcom/cal.com/blob/main/CONTRIBUTING.md)
- My code doesn't follow the style guidelines of this project
- I haven't commented my code, particularly in hard-to-understand areas
- I haven't checked if my changes generate no new warnings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High priority Created by Linear-GitHub Sync 🧹 Improvements Improvements to existing features. Mostly UX/UI platform Anything related to our platform plan
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant