First pass at DAP resolution

[mistermoe]

First pass at implementing DAP Resolution. There will almost certainly be some refactoring in subsequent PRs, but wanted to get something out that works.

Warning

• low test coverage
• test isn't using mocks
• not entirely sold on class names yet
• it feels like the word Resolver gets used 18,327 times. You'll see in the Usage section below

Usage

import 'package:dap/dap.dart';
import 'package:web5/web5.dart';

void main() async {
  final dap = Dap.parse('@moegrammer/didpay.me');
  print(dap.handle); // moegrammer
  print(dap.domain); // didpay.me
  print(dap.registryDid); // did:web:didpay.me
  print(dap); // @moegrammer/didpay.me

  // TODO: use mocks
  final resolver = DapResolver(DidResolver(
    methodResolvers: [DidWebResolver()],
  ));

  final result = await resolver.resolve(dap);
  print(result.moneyAddresses);
}

[wesbillman]

nit:
Since you're handing the orElse in the 2nd case, you might want to avoid force unwrapping the didDocument! in the first. Maybe something like:

final dapRegistryService = registryDidResolution.didDocument?.service.firstWhereOrNull((s) => s.type == 'DAPRegistry');
if (dapRegistryService == null) {
  throw DapResolutionException(
          'Registry DID does not have a DAPRegistry service');
}

(this code is probably wrong since I just wrote it in Github 😂 )

[wesbillman]

There's a few other places where force unwarpping is happening here too. Either way is cool, but I tend to lean towards never force unwrapping expect in specific cases in widget layout trees

[wesbillman]

nit:
You could grab the endpoint here so you don't need to use first below if you want.

final serviceEndpoint = dapRegistryService.serviceEndpoint.firstOrNull;
if (serviceEndpoint == null) {
  throw DapResolutionException('DAPRegistry service does not have a service endpoint');
}

// then below
registryEndpoint = Uri.parse(serviceEndpoint)

[mistermoe]

thanks for the comments @wesbillman ! I agree that force unwrapping is a footgun. created an issue to remove all force unwrapping in a subsequent PR: #4. Also created an issue in web5-dart to make didResolutionResult.didDocument not nullable because ... it shouldn't be! TBD54566975/web5-dart#93

[ethan-tbd]

thanks for the comments @wesbillman ! I agree that force unwrapping is a footgun. created an issue to remove all force unwrapping in a subsequent PR: #4. Also created an issue in web5-dart to make didResolutionResult.didDocument not nullable because ... it shouldn't be! TBD54566975/web5-dart#93

just saw this comment! latest commit actually closes TBD54566975/web5-dart#93 :))