switch from getDatasourceId to getNsPrefix #107

Closed
andreas.czerniak wants to merge 8 commits from stable_ids into stable_ids

Adding comments, test class, and important to handle datasource ids.

Adding comments, test class, and important to handle datasource ids.
andreas.czerniak added 8 commits 2021-05-13 00:11:20 +02:00
claudio.atzori reviewed 2021-05-14 15:27:49 +02:00
claudio.atzori requested changes 2021-05-14 15:32:11 +02:00
claudio.atzori left a comment
Owner

Summary:

  • clarify the reason for switching from datasourceId to nsPrefix
  • include test classes in the PR only when the tests are entirely defined
Summary: - clarify the reason for switching from datasourceId to nsPrefix - include test classes in the PR only when the tests are entirely defined
@ -60,3 +60,3 @@
final XsltCompiler comp = processor.newXsltCompiler();
QName datasourceIDParam = new QName(DATASOURCE_ID_PARAM);
comp.setParameter(datasourceIDParam, new XdmAtomicValue(value.getProvenance().getDatasourceId()));
comp.setParameter(datasourceIDParam, new XdmAtomicValue(value.getProvenance().getNsPrefix()));

DatasourceID and namespacePrefix are different concepts and are not interchangeable. Switching from one to the other should be done in accordance to the parameter name. With this PR it would still be bound to the param name varDataSourceId, creating confusion.

DatasourceID and namespacePrefix are different concepts and are not interchangeable. Switching from one to the other should be done in accordance to the parameter name. With this PR it would still be bound to the param name varDataSourceId, creating confusion.
@ -0,0 +9,4 @@
import org.mockito.junit.jupiter.MockitoExtension;
@ExtendWith(MockitoExtension.class)
public class PersonCleanerTest {

Please include the test classes in the PR when they provide actual assertions.

Please include the test classes in the PR when they provide actual assertions.
andreas.czerniak closed this pull request 2021-05-14 23:23:23 +02:00

Pull request closed

Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: D-Net/dnet-hadoop#107
No description provided.