This issue was caused by #180 which made sure that nested streams were
updated properly. Updating them properly caused nested takeUntil'd
streams to end too soon.
Coverage remained the same at 100.0% when pulling 4b0340c2d1fe1fa9cff85bd3a897bd8561fff4c4 on fix/takeUntil into 48799a9c6f5b0d223f32738e43846a7a4a65156f on master.
Coverage remained the same at 100.0% when pulling 4b0340c2d1fe1fa9cff85bd3a897bd8561fff4c4 on fix/takeUntil into 48799a9c6f5b0d223f32738e43846a7a4a65156f on master.
Coverage remained the same at 100.0% when pulling 4b0340c2d1fe1fa9cff85bd3a897bd8561fff4c4 on fix/takeUntil into 48799a9c6f5b0d223f32738e43846a7a4a65156f on master.
This issue was caused by #180 which made sure that nested streams were updated properly. Updating them properly caused nested takeUntil'd streams to end too soon.
This closes #188