Skip to content

Conversation

alex9smith
Copy link

This allows users to override the default expiry behavior when using DynamoDB TTL to expire sessions from the table. This would be useful, for example, if they wanted to use a browser session scoped cookie as the session cookie (with no maxAge attribute) but needed a shorter TTL than the default '1 day from now'.

If this parameter is not provided then there will be no change to the current behaviour. I think that means this can be released as a minor version change.

For full disclosure, the example I give about session cookies is exactly what I want to do.

This allows users to override the default expiry behavior when using
DynamoDB TTL to expire sessions from the table. This would be useful,
for example, if they wanted to use a browser session scoped cookie as
the session cookie (with no maxAge attribute) but needed a shorter TTL
than the default '1 day from now'.

If this parameter is not provided then there will be no change to the
current behaviour.
@alex9smith alex9smith force-pushed the feat/add-expiresin-option branch from 1983837 to c689574 Compare July 2, 2025 10:40
@alex9smith alex9smith force-pushed the feat/add-expiresin-option branch from c689574 to 2557bbf Compare July 2, 2025 10:55
@alex9smith alex9smith force-pushed the feat/add-expiresin-option branch from 2557bbf to 825094c Compare July 2, 2025 11:00
@alex9smith alex9smith force-pushed the feat/add-expiresin-option branch from 825094c to c703835 Compare July 2, 2025 11:21
Copy link

@liegeandlief liegeandlief 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, nice one for getting it done so quickly 🎸 Hopefully @ca98am79 will be able to take a look soon 🤞

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.

2 participants