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

regression: Inbox issue editor initialization #3025

Merged
merged 2 commits into from
Dec 7, 2023

Conversation

Palanikannan1437
Copy link
Collaborator

@Palanikannan1437 Palanikannan1437 commented Dec 7, 2023

Reverting back to old dependencies (changed in #3013) in useEffect hook of description form to fix random editor initialisation in Inbox issues.

Copy link

vercel bot commented Dec 7, 2023

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

6 Ignored Deployments
Name Status Preview Updated (UTC)
plane ⬜️ Ignored (Inspect) Dec 7, 2023 1:05pm
plane-dev ⬜️ Ignored (Inspect) Dec 7, 2023 1:05pm
plane-sh ⬜️ Ignored (Inspect) Dec 7, 2023 1:05pm
plane-sh-dev ⬜️ Ignored (Inspect) Dec 7, 2023 1:05pm
plane-sh-stage ⬜️ Ignored (Inspect) Dec 7, 2023 1:05pm
plane-staging ⬜️ Ignored (Inspect) Dec 7, 2023 1:05pm

@Palanikannan1437 Palanikannan1437 changed the title fixed core editor package build error [REGRESSION]: Inbox issue editor initialization Dec 7, 2023
@sriramveeraghanta sriramveeraghanta merged commit 2008413 into develop Dec 7, 2023
5 checks passed
@sriramveeraghanta sriramveeraghanta deleted the fix/inbox-issue-editor branch December 7, 2023 13:21
sriramveeraghanta pushed a commit that referenced this pull request Dec 7, 2023
* fixed core editor package build error

* reverting back changes such that editor doesn't rerender randomly in inbox issues
@Palanikannan1437 Palanikannan1437 changed the title [REGRESSION]: Inbox issue editor initialization regression: Inbox issue editor initialization Jan 31, 2024
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.

2 participants