Skip to content

feat: upgrade to react 18#1003

Closed
arunjaindev wants to merge 1 commit intofeat/react-vite-upgradefrom
feat/react-18
Closed

feat: upgrade to react 18#1003
arunjaindev wants to merge 1 commit intofeat/react-vite-upgradefrom
feat/react-18

Conversation

@arunjaindev
Copy link
Copy Markdown
Contributor

Description

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.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been 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

  • Test A
  • Test B

Checklist

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas

const CellComponent =
cell.component ?? (typeof cell.cellContent === 'string' ? cell.cellContent : null)
return CellComponent ? (
<div
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Missing key?

Base automatically changed from feat/markdown-editor to feat/day-picker February 4, 2026 13:01
@arunjaindev arunjaindev changed the base branch from feat/day-picker to feat/react-vite-upgrade April 6, 2026 07:53
@arunjaindev arunjaindev closed this Apr 6, 2026
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