-
-
Notifications
You must be signed in to change notification settings - Fork 26
Fix & modularize DataPackage fetch methods #2613
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
- Refactored the fetch method in DataPackage to return a Promise and handle options correctly. - Added detailed documentation for fetch method usage. - Improved error handling and retry logic for fetch method. - Added unit tests for DataPackage fetch method to ensure proper functionality. - Fixes the issue of a new resource map ID not being created on update Closes #2607
- Update and add corresponding unit tests Issue #2607
|
@vchendrix I was thinking about this and wonder if we should have an AppModel setting for the fetch timeout limit per file. Or if there's not one set, treat it as no timeout. What do you think? |
@robyngit sounds good |
|
@robyngit Sorry it took so long for me to review. I didn't see this. Lookint at it now. |
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.
Works great.
Default to never timing out, but allow setting a timeout in the appModel Issue #2607
- In editor, if a file fails to fetch ever after multiple retries, show an error message. Includes when there is a timeout and the file takes too long to fetch. - If the EML fails to fetch, show an error message in the metadata section. - The error styling is basic but better than showing a spinner forever. Issue #2607
Builds on top of @vchendrix changes in PR #2608