We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
users should be able to specify an expiration for a url. this expiration would exist as a new column in the sqlite database.
if a url was requested and it had a non-null expiration value, and the url is expired, it is deleted from the database and the api returns a 404.
create_url
expiration_date
1718479172174
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
users should be able to specify an expiration for a url. this expiration would exist as a new column in the sqlite database.
if a url was requested and it had a non-null expiration value, and the url is expired, it is deleted from the database and the api returns a 404.
game plan
create_url
to accept a new parameterexpiration_date
that is an epoch timestamp (like1718479172174
)create_url
store this timestamp in the new column for the url tableThe text was updated successfully, but these errors were encountered: