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

621: Save Metadata from FHIR Sender/Receiver/Number #985

Merged
merged 51 commits into from
Apr 11, 2024

Conversation

halprin
Copy link
Member

@halprin halprin commented Mar 28, 2024

Save Metadata from FHIR

This work bridges the work done in #982 and #983 by grabbing the data out of the FHIR resources and storing it into the database.

The vast majority of changes are adding the additional sender/receiver/number fields to PartnerMetadata and any other methods that pipe these fields to where it needs to go.

Because #982 isn't done yet, this PR is using dummy strings in SendOrderUseCase and SendResultUseCase. I feel like that PR should be merged in first before this one, so this PR will change slightly once that #982 is merged.

Issue

#621.

Checklist

  • I have added tests to cover my changes
  • I have added logging where useful (with appropriate log level)
  • I have added JavaDocs where required
  • I have updated the documentation accordingly

Note: You may remove items that are not applicable

@jcrichlake jcrichlake marked this pull request as ready for review April 2, 2024 20:10
@halprin halprin changed the title 621: Save Metadata from FHIR 621: Save Metadata from FHIR Sender/Receiver/Number Apr 2, 2024
Copy link
Contributor

@basiliskus basiliskus left a comment

Choose a reason for hiding this comment

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

Looks good to me. I guess this PR is waiting for implementation of the Order methods in PR #982

@saquino0827 saquino0827 marked this pull request as draft April 5, 2024 21:41
@saquino0827
Copy link
Contributor

Not sure why but I can't convert this PR back to a draft. I refactored this a bit from this PR being merged into main. Looking into setting up the our Dao with Postgresql jsonb datatypes and will update and fix test.

@saquino0827 saquino0827 marked this pull request as ready for review April 10, 2024 21:18
@jorg3lopez jorg3lopez force-pushed the story-621-save_new_metadata branch from 880cf82 to 0b1427d Compare April 11, 2024 17:25
metadata.receivedSubmissionId(),
false,
Types.VARCHAR),
new DbColumn("sent_message_id", metadata.sentSubmissionId(), true, Types.VARCHAR),
Copy link
Contributor

Choose a reason for hiding this comment

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

Thoughts on having final variables for the names?

Copy link
Member Author

Choose a reason for hiding this comment

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

It was already a comment earlier in this PR to remove the variable names and put them directly in the List.

Copy link
Member Author

@halprin halprin left a comment

Choose a reason for hiding this comment

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

@saquino0827, this looks awesome except for an accidental commit of a merge conflict file. There's also a recommendation to change an import.

Copy link

Copy link
Member Author

@halprin halprin left a comment

Choose a reason for hiding this comment

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

Oh, this is my PR. I can't technically approve it. ✅

Copy link
Contributor

@jorg3lopez jorg3lopez left a comment

Choose a reason for hiding this comment

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

Looks good, great work!

@saquino0827 saquino0827 merged commit 5e8be70 into main Apr 11, 2024
15 checks passed
@saquino0827 saquino0827 deleted the story-621-save_new_metadata branch April 11, 2024 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants