eca_cache: Action "Cache: write" has misleading description for "expire" setting

Issue information

From user: mxh

Contribution record

Fork management

Problem/Motivation

The action "Cache: write" has following description regarding the "expire" setting:

The lifetime in seconds until the cached value is considered invalid. Set to -1 for unlimited lifetime.

This may give the wrong assumption that this is the "max-age" value, such as 300 seconds until expiry. However, the "expire" setting requires a timestamp when the cached item starts to be invalid.

Steps to reproduce

Proposed resolution

Provide a description for better understanding. Maybe

The timestamp in seconds when the cached item expires.

Remaining tasks

User interface changes

API changes

Data model changes

Edited by drupalbot
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information