Sync Integration Checklist

If you want to integrate with our infrastructure, please follow these steps:

• Before starting any integration work, please reach out to us at chrome-sync-dev@google.com and share your plans / design doc! The Chrome Sync team will assign you a "champion" (primary contact person) to review your designs and code.
• If you're a Googler, please also file a bug via go/create-new-sync-data-type-bug
• Define your specifics proto in //components/sync/protocol/.
• Add it to the proto value conversions files.
• Add a field for it to [EntitySpecifics][EntitySpecifics].
• At this point, there are also some server-side integration steps to be done. They should be discussed in the thread or bug created above.
• Add it to the ModelType enum and kModelTypeInfoMap.
• Add to the SyncModelTypes enum in enums.xml and to the SyncModelType suffix in histograms.xml.
• If your type should have its own toggle in sync settings, add an entry to the UserSelectableType enum, add a preference for tracking whether your type is enabled, and map your type to the pref in GetPrefNameForType.
• Otherwise, if your type should be included in an existing toggle in sync settings, add it in GetUserSelectableTypeInfo.
• Register a ModelTypeController for your type in SyncApiComponentFactoryImpl::CreateCommonModelTypeControllers or platform-specific equivalent in ChromeSyncClient::CreateModelTypeControllers.
• Add your KeyedService dependency to SyncServiceFactory.
• Implement the actual data type logic. This will mostly be an implementation of the [ModelTypeSyncBridge][Bridge] interface.
• Write some integration tests.
• While rolling out your new data type, keep the Sync team in the loop! E.g. CC your assigned champion on all Finch CLs.
• If you're a Googler, please fill out go/sync-integration-feedback.