You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several definitions are currently being defined in FRP.BearRiver that,
in Yampa, are instead defined in an internal module FRP.Yampa.Switches.
To make it easier to port code over from Yampa to bearriver, we decide
to move those definitions into a matching module FRP.BearRiver.Switches
on the bearriver side.
The module is currently incomplete. Not all definitions from
FRP.Yampa.Switches exist in FRP.BearRiver. This commit moves only those
definitions that currently are being exported by FRP.BearRiver.
Several definitions are currently being defined in FRP.BearRiver that,
in Yampa, are instead defined in an internal module FRP.Yampa.EventS. To
make it easier to port code over from Yampa to bearriver, we decide to
move those definitions into a matching module FRP.BearRiver.EventS on
the bearriver side.
The module is currently incomplete. Not all definitions from
FRP.Yampa.EventS exist in FRP.BearRiver. This commit moves only those
definitions that currently are being exported by FRP.BearRiver.
The module FRP.Yampa.Conditional is being offered by Yampa, but not
bearriver. This makes the interface offered by bearriver not compliant
with Yampa, therefore not delivering on the promise of being
API-compatible.
This commit adds the module FRP.Yampa.Conditional into bearriver, as
FRP.BearRiver.Conditional.
The module
FRP.Yampa.Conditional
is being offered by Yampa, but notbearriver
.This makes the interface offered by
bearriver
not compliant withYampa
, therefore not delivering on the promise of being API-compatible.This is a subissue of #40. Because #40 is a big issue, it's good to split it in several smaller ones.
The text was updated successfully, but these errors were encountered: