Ticket #910 (closed task: fixed)

Opened 3 years ago

Last modified 3 years ago

Introduce Format Plugin validiation function

Reported by: dgollub Owned by: dgollub
Priority: high Milestone: OpenSync 0.39
Component: OpenSync: Format-Plugin API Version: 0.38
Severity: major Keywords:
Cc: bricks

Description

Format plugins should be able to register a validation function - which makes sure that the data of a OSyncChange/OSyncData is valid after an conversion.

This validation function should be optional.

If this function is available, this should get called for each entry after each conversion in a complete conversion path - to track down the broken conversion path/converter.

This also allows to drop the StaticMutex? and the RefCount? in the Entine for the OSyncXMLFormat Schema.

Change History

comment:1 Changed 3 years ago by dgollub

  • Status changed from new to assigned

comment:2 Changed 3 years ago by dgollub

  • Status changed from assigned to closed
  • Resolution set to fixed

Interface implementation got committed with r3824

comment:3 Changed 3 years ago by bricks

In my opinion we have to change the signature to pass user data (e.g. the xml schema) to the validate function. But where should the user data be loaded? Currently the init and finalize functions are part of the converter.

comment:4 Changed 3 years ago by dgollub

  • Component changed from OpenSync to OpenSync: Format-Plugin API
Note: See TracTickets for help on using tickets.