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

feat: replace old Status index with new StatusCreatedAt one #4691

Conversation

craigzour
Copy link
Contributor

@craigzour craigzour commented Nov 21, 2024

Summary | Résumé

Part 5 of #4287

  • Replaces use of old Status index with new StatusCreatedAt one
  • Loads the RemovalDate piece of information for each submission listed under Signed off for removal tab in an asynchronous way. This is due to the new index not returning the RemovalDate data in its projected attributes.

Tests

  • On the response page (in all tabs): make sure you can still see all form submissions you were getting before testing the new index. The only difference should be that items are now ordered by CreatedAt date. It means that the oldest response should be at the top of the list.
  • On the response page (tab: Signed off for removal): items should asynchronously load their "Next step" piece of information.

Testing options:

@craigzour craigzour self-assigned this Nov 21, 2024
@craigzour craigzour changed the title Feature/replace old status index with new status created at index feat: replace old status index with new status created at index Nov 21, 2024
@craigzour craigzour changed the title feat: replace old status index with new status created at index feat: replace old Status index with new StatusCreatedAt one Nov 21, 2024
Copy link
Contributor

@craigzour craigzour force-pushed the feature/replace-old-status-index-with-new-status-created-at-index branch 4 times, most recently from 3f16502 to 0279082 Compare November 27, 2024 16:44
@craigzour craigzour force-pushed the feature/replace-old-status-index-with-new-status-created-at-index branch from 0279082 to f7d4435 Compare December 2, 2024 14:31
@craigzour craigzour marked this pull request as ready for review December 2, 2024 14:31
}, []);

if (label === null) {
return <Skeleton count={1} className="my-4 ml-4 w-[300px]" />;
Copy link
Member

Choose a reason for hiding this comment

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

👍

timarney
timarney previously approved these changes Dec 2, 2024
Copy link
Member

@timarney timarney left a comment

Choose a reason for hiding this comment

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

Nice work on this + all the previous steps to get to this point.

Copy link
Contributor

@thiessenp-cds thiessenp-cds left a comment

Choose a reason for hiding this comment

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

I tested the responses tabs and the submissions are in order.
Testing the download formats, the submissions could be out of order. I added a quick sort() call on that to make sure they'd be in order. Kind of out scope of this PR but nice to fix now when it's obvious.
Nice work! LGTM :)

@craigzour craigzour merged commit 9b1caf9 into main Dec 2, 2024
13 checks passed
@craigzour craigzour deleted the feature/replace-old-status-index-with-new-status-created-at-index branch December 2, 2024 20:38
craigzour added a commit that referenced this pull request Dec 3, 2024
craigzour added a commit that referenced this pull request Dec 3, 2024
craigzour added a commit that referenced this pull request Dec 3, 2024
craigzour added a commit that referenced this pull request Dec 3, 2024
craigzour added a commit that referenced this pull request Dec 10, 2024
craigzour added a commit that referenced this pull request Dec 10, 2024
…4691)" (#4761) (#4763)

* Reapply "feat: replace old Status index with new StatusCreatedAt one (#4691)" (#4761)

This reverts commit 78a8457.

* fix DynamoDB request configuration when no Status#CreatedAt need to be passed in
craigzour added a commit that referenced this pull request Dec 11, 2024
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.

3 participants