-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[UI] Ember Data Migration - Tools Lookup Component #30014
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
Conversation
|
Build Results: |
|
CI Results: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why the diff isn't showing since I just renamed the file like the other PR's 🤷♂️
| const { creationTime, creationTtl } = this.lookupData; | ||
| if (creationTime && creationTtl) { | ||
| // returns new Date with seconds added. | ||
| return addSeconds(creationTime, Number(creationTtl)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
creationTime returns as an instance of Date so we don't need parseISO.
| assert.true(flashSuccessSpy.calledWith('Lookup was successful.'), 'it renders success flash'); | ||
| assert.dom(GENERAL.infoRowValue('Creation path')).hasText(data.creation_path); | ||
| assert.dom(GENERAL.infoRowValue('Creation time')).hasText(data.creation_time); | ||
| assert.dom(GENERAL.infoRowValue('Creation time')).hasText(now.toString()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.

Description
This PR converts the
tools/lookupcomponent to ts and updates it to use the api service.TODO only if you're a HashiCorp employee
backport/label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x, but older release branches will bebackport/ent/x.x.x+ent.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.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.