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

UI: Use timestamp.now() in custom messages #29525

Merged
merged 5 commits into from
Feb 7, 2025

Conversation

hellobontempo
Copy link
Contributor

@hellobontempo hellobontempo commented Feb 7, 2025

Description

This replaces new Date() with timestamp.now() which can be more reliable stubbed in tests. See #19521 for more context

✅ enterprise tests (because of timezone weirdness, double checked enterprise tests by opening a PR to the enterprise repo)

TODO only if you're a HashiCorp employee

  • Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
    • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
  • ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
    of a public function, even if that change is in a CE file, double check that
    applying the patch for this PR to the ENT repo and running tests doesn't
    break any tests. Sometimes ENT only tests rely on public functions in CE
    files.
  • Jira: If this change has an associated Jira, it's referenced either
    in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.
  • ENT PR: If this change has an associated ENT PR, please link it in the
    description. Also, make sure the changelog is in this PR, not in your ENT PR.

@hellobontempo hellobontempo added this to the 1.18.5 milestone Feb 7, 2025
@hellobontempo hellobontempo requested a review from a team as a code owner February 7, 2025 01:21
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Feb 7, 2025
Copy link

github-actions bot commented Feb 7, 2025

Build Results:
All builds succeeded! ✅

Copy link

github-actions bot commented Feb 7, 2025

CI Results:
All Go tests succeeded! ✅

@@ -46,11 +49,14 @@ module('Integration | Component | messages/page/create-and-edit', function (hook
assert.dom(CUSTOM_MESSAGES.field('message')).exists();
assert.dom('[data-test-kv-key="0"]').exists();
assert.dom('[data-test-kv-value="0"]').exists();
assert.dom(CUSTOM_MESSAGES.input('startTime')).exists();
Copy link
Contributor Author

Choose a reason for hiding this comment

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

redundant 🧹

assert
.dom(CUSTOM_MESSAGES.input('startTime'))
.hasValue(format(addDays(startOfDay(timestamp.now()), 1), datetimeLocalStringFormat));
assert.dom(CUSTOM_MESSAGES.input('endTime')).exists();
Copy link
Contributor Author

Choose a reason for hiding this comment

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

redundant 🧹

@hellobontempo hellobontempo merged commit 9e6b5ce into main Feb 7, 2025
32 of 33 checks passed
@hellobontempo hellobontempo deleted the ui/VAULT-33866/fix-timestamp-custom-messages branch February 7, 2025 23:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/1.18.x hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-changelog ui
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants