Fix #382: Make Gradient data_id optional to prevent tutorial errors

[pxkundu]

Fix #382: Make Gradient data_id optional to prevent tutorial errors

Problem

Tutorial notebooks fail with ValueError: The data_id should not be None when users create Gradient objects without providing the required data_id parameter. This breaks the learning experience for new users following documentation examples.

Root Cause

The Gradient.__init__ method enforced that data_id must be provided, raising a ValueError if None:

if self.data_id is None:
    raise ValueError("The data_id should not be None.")

This was problematic for tutorial scenarios where users manually create Gradient objects without understanding the internal data tracking requirements.

Solution

• ✅ Remove the ValueError when data_id is None
• ✅ Auto-generate default data_id using pattern gradient_{gradient_id} when None
• ✅ Maintain full backward compatibility with existing explicit data_id usage
• ✅ Ensure unique data_ids for each gradient to prevent conflicts
• ✅ Preserve all existing functionality while making the API more user-friendly

Before (Problematic):

# This would raise ValueError in tutorials
gradient = Gradient(
    from_response=response_param,
    to_pred=pred_param,
    score=0.8
    # data_id=None causes ValueError
)

After (Fixed):

# This now works seamlessly
gradient = Gradient(
    from_response=response_param,
    to_pred=pred_param,
    score=0.8
    # data_id=None automatically becomes "gradient_{uuid}"
)

Benefits

• 📚 Tutorial Friendly: New users can follow examples without encountering errors
• 🔄 Backward Compatible: All existing code with explicit data_id continues to work
• 🎯 User Experience: Reduces friction for learning and experimentation
• 🛡️ Robust Defaults: Auto-generated data_id values are unique and predictable
• 📖 Better Documentation: Tutorials can focus on concepts rather than internal details

Testing

• ✅ Verified explicit data_id still works (backward compatibility)
• ✅ Confirmed data_id=None generates sensible defaults
• ✅ Tested missing data_id parameter works with auto-generation
• ✅ Validated unique data_id generation for multiple gradients
• ✅ Ensured tutorial scenarios work without errors
• ✅ Confirmed integration with existing codebase

Impact

This fix resolves a common barrier for new users learning AdalFlow through tutorials and documentation. Users can now create Gradient objects intuitively without needing to understand internal data tracking mechanisms.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Improves user experience and tutorial usability

Fixes #382