-
Notifications
You must be signed in to change notification settings - Fork 0
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
🐛 Correct properties for attachment model #31
Conversation
Stricter types can be used for objectType and type, which was the case for the old attachment model, so we should continue that here.
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.
Since, we're enriching attachment definition, I would take the opportunity to remove unused variable COST_ATTACHMENT_VALUE
that is duplicated from attachmentVersion.ts
, where it is actually used. Both were added in f59ddc1
Can I take this PR to sneak in a commit that removes this code comment since it doesn't belong after the changes we did today in 948d97d?
Also, what are your plans for HPC-8205 branch that removes |
sounds good to me
That's still a WIP that i need to evolve a bit more, but i'll just rebase that ontop of whatever other changes we have in |
@Pl217 done |
4514cb8
to
5963b71
Compare
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 have also bumped version here, because I will publish a new version once this PR is merged, since changes from #25 are needed for https://github.com/UN-OCHA/hpc_service/pull/2445
Stricter types can be used for objectType and type, which was the case
for the old attachment model, so we should continue that here.