Client-side script: If an error is thrown in a Deferred callback, this error doesn't appear in the console, which makes debugging more difficult
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, jquery
- Domain
- frontend
Research direction
Start with the CodePen example and the two console samples comparing native Promise.then with $.Deferred().then. Review the linked commit where .done changed to .then and trace how errors from the callback are handled. Done means an error thrown in a Deferred callback appears in the browser console.
Written by the indexing model from the issue text.
Description
CodePen example: https://codepen.io/pomah33/pen/MWrRKMb?editors=0010
If an error was thrown in Deferred callback, this error doesn't appear in console, which makes debugging more difficult
Error possibly was caused by this PR: https://github.com/DevExpress/DevExtreme.AspNet.Data/commit/6d973700bd28e4440aa05e267fb255202b87d395#diff-24d8a479ae56566c65690364aa2156fff7613fd38bd024153579f15d92b26f91L73, when deferred-like method .done was changed to promise-like .then
But on error in 'then' section of deferred (not promise) hides without appearing in console
Samples to try in dev console:
new Promise((resolve) => { window.r1 = resolve; }).then(() => { throw new Error('my error'); })
r1()
const d = new $.Deferred()
d.then(() => { throw new Error('my error'); })
d.resolve()
- Dominant language
- C#
- Stars
- 165
- Forks
- 140
- Avg merge
- 12h 48m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DevExpress/DevExtreme.AspNet.Data
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
DevExpress/DevExtreme.AspNet.Data#588 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Dependency DashboardOpen
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
ES6 supportOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in DevExpress/DevExtreme.AspNet.Data
Similar issues
-
copilot documentation
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
elsa-workflows/elsa-foundation#2290 ·
Maintainers usually reply within 1 day
-
python triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/semantic-kernel#14522 ·
Maintainers usually reply within 4 days
-
area-integrations needs-area-label triage:bot-seen triage:needs-human
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/aspire#20652 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
agoda-com/Shouldly.FromAssert#40 ·
Maintainers usually reply within 1 day