-
Notifications
You must be signed in to change notification settings - Fork 7
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
Ctskf 832 - CCCD - Allow for multiple documents on a message #8064
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've left some comments and questions - happy to discuss if you like 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
536f5d2
to
e75e45a
Compare
refine the original changes on top of CTSKF-1002
e75e45a
to
f48eb9d
Compare
f48eb9d
to
ed68d1f
Compare
Quality Gate passedIssues Measures |
Ticket:
CCCD - Allow for multiple documents on a message
https://dsdmoj.atlassian.net/browse/CTSKF-832
241006 updates:
Changed the attachment variable name to attachments (plural for multiple). New attachments (one) can be added and download afterwards. The old attachment did not work anymore. Fixed by updating the name column in active_storage_attachments.
241025 updates:
Tried to modified rspec tests to pass.
Accidentally fixed the issue for remove file link not showing for attachments.
250113 updates:
Checked out a new branch to refine the changes did before on top of CTSKF-1002.
No idea why there is no change in blob count, will further investigate
250122 updates:
Passed all the tests but there are some uncertainties.
spec/models/message_spec.rb:
Commented out the tests for blob count change. This test may not be applicable when we move on to CTSKF-833 where we create the attachments as documents. Thus the blob will still exist after we remove the message.
features/step_definitions/messaging_steps.rb:
Not sure if it is OK not using those hooks.