Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SO-5842: core API changes to support resource agnostic upgrade mechanism #1193

Merged
merged 28 commits into from
Aug 18, 2023

Conversation

cmark
Copy link
Member

@cmark cmark commented Aug 16, 2023

No description provided.

@cmark cmark added the feature label Aug 16, 2023
@cmark cmark requested review from apeteri and nagyo August 16, 2023 17:02
@cmark cmark self-assigned this Aug 16, 2023
@cmark cmark marked this pull request as draft August 16, 2023 17:03
@cmark cmark marked this pull request as ready for review August 17, 2023 14:13
Copy link
Member

@apeteri apeteri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🍏

Copy link
Member

@nagyo nagyo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with some minor notes that should be addressed later

});

protected final void expandDependencyUpgrades(List<R> results) {
if (!expand().containsKey("dependencies_upgrades")) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought that we are following java naming conventions for expand keywords? E.g. inboundRelationships, statedDescendants, referenceSet. The wording should probably follow the method's name or the other way around, e.g. dependencyUpgrades, upgradeDependencies

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would also be nice to save this in a static field somewhere, like:

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a temporary expand key, we need dot notation support here, like this dependencies.upgrades() but unfortunately the current expand parser does not like dots in property names and fails to parse the object. A minor refactor is required to make it work so we had to use underscore instead of dot for the separator.

concept = getConcept(upgradeCodeSystem.getResourceURI(), moduleId);
assertEquals(effectiveTime, concept.getEffectiveTime());
}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't forget to add back or refactor these unit tests later on.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, that's on my to-do list.

return extensionConcept.getDescriptions().getItems().stream().filter(d -> d.getTerm().equals(extensionFsnTerm)).findFirst().get();
}

}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same for these

@nagyo nagyo merged commit a22583f into 9.x Aug 18, 2023
1 check passed
@nagyo nagyo deleted the feature/SO-5842-resource-agnostic-upgrades branch August 18, 2023 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants