-
Notifications
You must be signed in to change notification settings - Fork 13
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
DNM -- feat: scheduler dialog on dataset route #1653
Conversation
There hasn't been any activity on this pull request in the past 3 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days. If you want this PR to never become stale, please apply the "Draft" label. |
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.
LGTM so far w/ a very minor suggestion.
There hasn't been any activity on this pull request in the past 3 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days. If you want this PR to never become stale, please apply the "Draft" label. |
Closing after discussion with Sean and Caleb. This epic is pivoting in a healthier, long-term direction. |
Please do not delete this PR, we may want these utils down the road. |
@sonofflynn89 -- can you double check I'm not being a dummy here? I know we've run into this issue before where we try switching this between
IRequestOptions
andIHubRequestOptions
. Adding this extra conditional allows me to get the schedule on the /downloads route, but without it, it's undefined every time.Closes Issues: https://devtopia.esri.com/dc/hub/issues/11446
Updated meaningful TSDoc to methods including Parameters and Returns, see Documentation Guide
used semantic commit messages
PR title follows semantic commit format (CRITICAL if the title is not in a semantic format, the release automation will not run!)
updated
peerDependencies
as needed. CRITICAL our automated release system can not be counted on to updatepeerDependencies
so we must do it manually in our PRs when needed. See the updating peerDependencies section of the release instructions for more details.