-
Notifications
You must be signed in to change notification settings - Fork 108
New resource detector for DigitalOcean #382
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
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #382 +/- ##
============================================
+ Coverage 82.14% 82.30% +0.16%
- Complexity 1801 1817 +16
============================================
Files 137 138 +1
Lines 7594 7664 +70
============================================
+ Hits 6238 6308 +70
Misses 1356 1356 Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
Could the |
Interesting! I saw they existed but didn't look into them. Yeah I can use them... it feels "hacky" to have the |
There are only a couple existing contrib resource detectors, so I could be doing something wildly off here.
Current things I'm iffy on:
file
autoload and replacing with @Nevay's SPI loader, but I wasn't sure if that was possible to implement now.file_get_contents
anderror_log
... I've seen a few SDK utility methods built around these, but the readfile was private so not reusable in the production code, and I was unsure how to best handle the SDK logging for PHPUnit.I'm marking this as draft until I get a chance to test it live.