added new sync_to_synapse method

[andrewelamb]

Problem:

The syncToSynapse function doesn't fit the new OOP model paradigm.

Solution:

• A new sync_to_synapse method was added to the StorableContainer class
• syncToSynapse was deprecated

Testing:

• Unit tests for the new helper functions
• Integration tests for the new sync_to_synapse method

[andrewelamb]

Code review

Found 2 issues:

1. "dataFileSizeBites" appears to be a typo for "dataFileSizeBytes" in NON_ANNOTATION_COLUMNS and docs. The integration test at test_dataset_async.py:44 uses "dataFileSizeBytes", confirming the correct spelling. With the typo, this column would not be recognized as a non-annotation column and would instead be treated as a user annotation during manifest upload, silently corrupting metadata.

synapsePythonClient/synapseclient/models/services/manifest.py

Lines 59 to 61 in 9a15057

	"versionNumber",
	"dataFileSizeBites",
	"createdBy",

synapsePythonClient/docs/explanations/manifest_csv.md

Lines 46 to 48 in 9a15057

	| versionNumber | version of the file |
	| dataFileSizeBites | size of the file in bytes |
	| createdBy | user who created the file |

2. The new sync_to_synapse validates that the manifest contains a "parentId" column, but the existing generate_sync_manifest (and REQUIRED_FIELDS in sync.py) uses "parent" as the column name. A manifest generated by generate_sync_manifest and then passed to project.sync_to_synapse() will raise ValueError: Manifest must contain a 'parentId' column. The tutorial at upload_data_in_bulk.py demonstrates exactly this broken workflow.

synapsePythonClient/synapseclient/models/services/manifest.py

Lines 375 to 377 in 9a15057

	# Validate required columns before attempting any column-dependent operations
	for col in ("path", "parentId"):
	if col not in df.columns:

synapsePythonClient/synapseutils/sync.py

Lines 56 to 57 in 9a15057

	REQUIRED_FIELDS = ["path", "parent"]
	FILE_CONSTRUCTOR_FIELDS = ["name", "id", "synapseStore", "contentType"]

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}