Page MenuHomePhabricator

[Task] Split RDF mapping code into separate classes per type
Closed, ResolvedPublic


RDF mappings for the different value types (and property data types) is currently located in two big classes, SimpleValueRdfBuilder and ComplexValueRdfBuilder. They should be split up by data type, to improve maintainability and testability. This would also make it more streight forward to add mappings for new data types.

Event Timeline

daniel claimed this task.
daniel raised the priority of this task from to Medium.
daniel updated the task description. (Show Details)
daniel added subscribers: Tobi_WMDE_SW, hoo, Smalyshev and 4 others.

Change 252026 had a related patch set uploaded (by Daniel Kinzler):
[WIP] Split SimpleValueRdfBuilder and ComplexValueRdfBuilder

daniel renamed this task from Split RDF mapping code into separate classes per type to [Task] Split RDF mapping code into separate classes per type.Nov 12 2015, 9:11 PM
daniel set Security to None.

@Tobi_WMDE_SW I split this out of the original patch for T112083. It's unclear to me whether we want to commit to this in the current sprint. I'm confident that I can get the code finished on monday, but we'll not get this through review before the sprint ends. So, what do you recommend? Commit to this and keep working on it Kanban-style, or push it into the next sprint Scrum-style?

Change 252026 merged by jenkins-bot:
Split SimpleValueRdfBuilder and ComplexValueRdfBuilder