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

[BUG] $logday does not account for user timezone when identifying the date #1

Open
antoniolofiego opened this issue Mar 22, 2021 · 0 comments
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@antoniolofiego
Copy link
Collaborator

The current implementation of $logday automatically assumes GMT timezone for every logged day.

collector.on('collect', (message) => { const timestamp = new Date(message.createdAt); payload = { user_id: message.author.id, message: message.content, log_date: timestamp.toLocaleDateString('en-US'), }; });

Need to change how the message.createdAt gets parsed, while maintaining the formatting pre-PUT into DynamoDB.

@antoniolofiego antoniolofiego added bug Something isn't working good first issue Good for newcomers labels Mar 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant