Skip to content

Conversation

@ZhengZhenyu
Copy link
Collaborator

Description

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)
  • 📝 Documentation update
  • 🔧 Configuration change
  • 🎨 Code refactoring (no functional changes)
  • ⚡️ Performance improvement
  • ✅ Test addition or update

Related Issues

Closes #
Related to #

Changes Made

Database Changes

  • No database changes
  • New tables added
  • Existing tables modified
  • Migration script included: alembic/versions/XXXXX_*.py
  • Migration tested locally
  • Rollback tested

Testing

Test Coverage

  • Unit tests added/updated
  • Integration tests added/updated
  • Manual testing completed
  • Test script provided

Test Instructions

# How to test these changes

Screenshots (if applicable)

Checklist

Code Quality

  • Code follows project style guidelines
  • Self-review completed
  • Comments added for complex logic
  • No console.log or debug statements left
  • No commented-out code left

Functionality

  • All tests pass locally
  • No breaking changes (or documented if necessary)
  • Error handling implemented
  • Edge cases considered

Security

  • No sensitive data in code
  • Input validation added
  • Authentication/authorization checked
  • Dependencies are up to date

Documentation

  • Code is self-documenting or commented
  • API documentation updated (if applicable)
  • README updated (if applicable)
  • Migration guide provided (if applicable)

Deployment Notes

  • No special deployment steps needed
  • Database migration required
  • Environment variables need update
  • Configuration files need update

Migration Instructions

# Step-by-step migration instructions
cd backend
alembic upgrade head

Performance Impact

  • No performance impact
  • Improves performance
  • May impact performance (details below)

Backward Compatibility

  • Fully backward compatible
  • Requires manual migration
  • Breaking changes (migration guide included)

Additional Notes


AI Assistance Declaration

  • AI assistance used (Claude, GitHub Copilot, etc.)
  • All AI-generated code reviewed and tested
  • Co-authored-by tag included in commit

🤖 This PR follows the contribution guidelines

ZhengZhenyu and others added 2 commits February 10, 2026 14:52
Use FullCalendar's official Draggable API to enable bidirectional
drag-and-drop between the unscheduled content panel and the calendar:

- Drag unscheduled items onto calendar dates to schedule them
- Drag calendar events back to the unscheduled panel to unschedule
- Visual feedback: panel highlights with dashed border on drag-over,
  items show reduced opacity while being dragged
- Auto-reinitialize Draggable when content list or panel state changes
- Proper lifecycle cleanup on component unmount

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…ling

feat: implement drag-and-drop scheduling for content calendar
@ZhengZhenyu ZhengZhenyu merged commit 5dc7f38 into opensourceways:main Feb 10, 2026
3 of 6 checks passed
@opensourceways-bot
Copy link

CLA Signature Guide

@ZhengZhenyu , thanks for your pull request.

The following commit(s) are not associated with a signed Contributor License Agreement (CLA).

Commit Reason
e00c3b5b feat: implement drag-and-drop sc... the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the CLA.
17ffa9cf Merge pull request #1 from Zheng... the email used in the commit is not linked to a signed CLA!
please verify that it matches the email you used when signing the CLA.

To sign CLA, click here.

To check if your email is configured correctly, refer to the FAQs.

Once you've signed the CLA or updating your email, please comment /check-cla to revalidate CLA status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants