Alec Hill

…so that only the owner being destroyed removes drawer lifecycle handling. Otherwise drawer modules become unresponsive when any activity is destroyed. See https://github.com/palaima/DebugDrawer/issues/98

If an activity that does not own the drawer gets destroyed, `DebugDrawerLifecycleCallbacks` `onActivityDestroyed(Activity activity)` de-registers the lifecycle hooks for the drawer and its modules This manifests in the drawer modules...

… requests Fixes #50 and a couple of related minor issues I can also see that the same issues may apply to the the @Field and parts resolver, but have...

Given an endpoint has optional args mapped to query or header params... ```typescript @GET("/something") @Queries({ ping: 'pong' }) async getSomethingWithOptionalQuery(@Query('since') since?: string, @QueryMap filters?: Record): Promise { return {} };...