Rewriting my portfolio site to be self-hosted and not just a static site led to me screwing around with miette, which then led to me making a helpful error page for when i fuck up something during development. This was totally a worthwhile use of 3 hours today.
November 22, 2024 at 1:45 AM
Rewriting my portfolio site to be self-hosted and not just a static site led to me screwing around with miette, which then led to me making a helpful error page for when i fuck up something during development. This was totally a worthwhile use of 3 hours today.
This is what proper error debugging can look like in #Swift 6:
AppError
└─ ProfileError
└─ DatabaseError
└─ FileError.notFound(path: "/Users/data.db")
Learn how to achieve this full error chain visibility in your apps with a simple protocol!
#Debugging #iOSDev
www.fline.dev/swift-6-type...
AppError
└─ ProfileError
└─ DatabaseError
└─ FileError.notFound(path: "/Users/data.db")
Learn how to achieve this full error chain visibility in your apps with a simple protocol!
#Debugging #iOSDev
www.fline.dev/swift-6-type...
www.fline.dev
May 2, 2025 at 2:22 PM
This is what proper error debugging can look like in #Swift 6:
AppError
└─ ProfileError
└─ DatabaseError
└─ FileError.notFound(path: "/Users/data.db")
Learn how to achieve this full error chain visibility in your apps with a simple protocol!
#Debugging #iOSDev
www.fline.dev/swift-6-type...
AppError
└─ ProfileError
└─ DatabaseError
└─ FileError.notFound(path: "/Users/data.db")
Learn how to achieve this full error chain visibility in your apps with a simple protocol!
#Debugging #iOSDev
www.fline.dev/swift-6-type...
Basically this:
I can wrap any of the specific errors coming out of various libraries into a custom error type that I can then use throughout my application so most of my code doesn't need to know about the specifics of each library while still being able to react to different error types.
I can wrap any of the specific errors coming out of various libraries into a custom error type that I can then use throughout my application so most of my code doesn't need to know about the specifics of each library while still being able to react to different error types.
![use std::{error, fmt, io};
#[allow(dead_code)]
#[derive(Debug)]
pub enum AppError {
RuntimeError,
RenderError,
ImageError(image::ImageError),
IoError(io::Error),
}
impl fmt::Display for AppError {
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
write!(f, "{:?}", self)
}
}
impl error::Error for AppError {}](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:u3kjbm2q66tdwlyxyewgbdsf/bafkreid6w7fxs7ftutngqlsbw6qpkguwv664d6b6n2dggs64wituillmsm@jpeg)
August 5, 2025 at 11:26 AM
Basically this:
I can wrap any of the specific errors coming out of various libraries into a custom error type that I can then use throughout my application so most of my code doesn't need to know about the specifics of each library while still being able to react to different error types.
I can wrap any of the specific errors coming out of various libraries into a custom error type that I can then use throughout my application so most of my code doesn't need to know about the specifics of each library while still being able to react to different error types.
So, I can just use my "AppError" as the type signature and let errors bubble up to wherever I want to handle them and only that error handling code may need to now the specifics but may also just write a generic log line, depending on what error it is.
August 5, 2025 at 11:26 AM
So, I can just use my "AppError" as the type signature and let errors bubble up to wherever I want to handle them and only that error handling code may need to now the specifics but may also just write a generic log line, depending on what error it is.
Seeing the “Snapchat is a Camera App” error on your iPhone? 📸 We’ve got the fix ready and waiting—check out the full guide:
www.izoate.com/blog/how-to-...
#SnapchatFix #iPhoneHelp #AppError #TechTips #MobileTroubleshooting
www.izoate.com/blog/how-to-...
#SnapchatFix #iPhoneHelp #AppError #TechTips #MobileTroubleshooting
How to Fix “Snapchat Is a Camera App” Error on iPhone - Izoate
Facing the "Snapchat is a camera app" error on iPhone? Learn how to fix missing camera options, and resolve the issue with effective troubleshooting steps.
www.izoate.com
November 10, 2025 at 7:06 AM
Seeing the “Snapchat is a Camera App” error on your iPhone? 📸 We’ve got the fix ready and waiting—check out the full guide:
www.izoate.com/blog/how-to-...
#SnapchatFix #iPhoneHelp #AppError #TechTips #MobileTroubleshooting
www.izoate.com/blog/how-to-...
#SnapchatFix #iPhoneHelp #AppError #TechTips #MobileTroubleshooting