LinkException as a sealed class

[RobertBrunhage]

If LinkException would use a sealed class then we would be enforced to handle/decide not to handle, different exceptions.

Right now I go in to the source code to see what I want to handle, such as HttpLinkParserException etc

gql/links/gql_link/lib/src/exceptions.dart

Lines 5 to 18 in 03186c8

	@immutable
	abstract class LinkException implements Exception {
	/// The original exception causing this exception
	final Object? originalException;
	final StackTrace? originalStackTrace;
	const LinkException(
	this.originalException,
	this.originalStackTrace,
	);
	@override
	String toString() => "LinkException($originalException, $originalStackTrace)";
	}

Not sure if there are technical limitations for why this is not the case or if it just hasn't been updated, wanted to make the ticket either way!

[knaeckeKami]

in the current architecture, LinkException cannot be sealed because various link implementations (which are in different packages, e.g. gql_http_link, gql_dio_link, gql_websocket_link) use different implementations of exceptions which might attack more information on what happened.