Skip to content

Add a 'createdAt' time when persisting new Iconik projects#1507

Merged
bryophyta merged 2 commits intomainfrom
pf/add-createdAt-to-iconik-projects-model
Apr 27, 2026
Merged

Add a 'createdAt' time when persisting new Iconik projects#1507
bryophyta merged 2 commits intomainfrom
pf/add-createdAt-to-iconik-projects-model

Conversation

@bryophyta
Copy link
Copy Markdown
Contributor

@bryophyta bryophyta commented Mar 18, 2026

What does this change?

Add a 'created at' time when we store new Iconik projects. This is an optional field, so it shouldn't cause any issues for existing projects. The main use-case that we're anticipating at the moment is that it will allow ordering or filtering by time created. Generally speaking, the value in this is to surface the most recent projects first. So that means we can afford to defer the question of whether/how to backfill the creation date for old projects.

How has this change been tested?

  • Deploy to CODE, create a project, verify that its 'created at' date is populated in the DynamoDB table.

How can we measure success?

Have we considered potential risks?

Images

Accessibility

@bryophyta bryophyta added the feature Departmental tracking: work on a new feature label Mar 18, 2026
@bryophyta bryophyta force-pushed the pf/add-createdAt-to-iconik-projects-model branch from 387d05d to 6f262f4 Compare March 18, 2026 17:28
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 18, 2026

@bryophyta bryophyta marked this pull request as ready for review April 8, 2026 08:26
@bryophyta bryophyta requested a review from a team as a code owner April 8, 2026 08:26
Comment on lines +100 to +103
createdAt = Some(
createdAt
.format(java.time.format.DateTimeFormatter.ISO_DATE_TIME)
)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Won't this replace the createdAt time every time a project is upserted? ie. this field would be a lastModifiedAt

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

yes it would. I did wonder about this but convinced myself it was fine because I don't think we have any expectation of a project being upserted more than once, as it stands.

but on reflection I think you're right 👍 I'll take a look at this later

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

added a new commit which should address this: 9ecf022

@bryophyta bryophyta force-pushed the pf/add-createdAt-to-iconik-projects-model branch from c2fd054 to 9ecf022 Compare April 9, 2026 07:52
@bryophyta bryophyta force-pushed the pf/add-createdAt-to-iconik-projects-model branch from 9ecf022 to 9f8b70c Compare April 27, 2026 12:48
@bryophyta bryophyta merged commit 70c72de into main Apr 27, 2026
5 checks passed
@bryophyta bryophyta deleted the pf/add-createdAt-to-iconik-projects-model branch April 27, 2026 14:45
@gu-prout
Copy link
Copy Markdown

gu-prout Bot commented Apr 27, 2026

Seen on PROD (merged by @bryophyta 5 minutes and 31 seconds ago) Please check your changes!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature Departmental tracking: work on a new feature Seen-on-PROD

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants