defold / defold/extension-firebase-crashlytics
dmLogError and dmLogFatal should be reportes separatly as issues in crashlytics
Open
- Dominant language
- C++
- Stars
- 5
- Forks
- 0
- Avg merge
- 19h 9m
- Merged PRs (30d)
- 1
Description
It should be reported the same way Lua errors reported
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating dmLogError and dmLogFatal, then trace the existing path used to report Lua errors to Crashlytics. Confirm how those log calls are currently grouped and compare the expected separate-issue behavior; done means each error type is reported separately in Crashlytics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, lua
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100