Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bearriver: Offer all definitions from FRP.Yampa.EventS #400

Closed
ivanperez-keera opened this issue Dec 22, 2023 · 0 comments
Closed

bearriver: Offer all definitions from FRP.Yampa.EventS #400

ivanperez-keera opened this issue Dec 22, 2023 · 0 comments
Assignees
Milestone

Comments

@ivanperez-keera
Copy link
Owner

The module FRP.Yampa.EventS 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 is a subissue of #40. Because #40 is a big issue, it's good to split it in several smaller ones.

ivanperez-keera added a commit that referenced this issue Feb 22, 2024
Several definitions are currently being defined in FRP.BearRiver that,
in Yampa, are instead defined in an internal module FRP.Yampa.Hybrid. To
make it easier to port code over from Yampa to bearriver, we decide to
move those definitions into a matching module FRP.BearRiver.Hybrid on
the bearriver side.

The module is currently incomplete. Not all definitions from
FRP.Yampa.Hybrid exist in FRP.BearRiver. This commit moves only those
definitions that currently are being exported by FRP.BearRiver, which
EventS depends on.
ivanperez-keera added a commit that referenced this issue Feb 22, 2024
The module FRP.BearRiver.EventS does not contain all definitions offered
by its Yampa counterpart. This makes the interface offered by bearriver
not compliant with Yampa, therefore not delivering on the promise of
being API-compatible.

This commit adds missing definitions to the module FRP.BearRiver.EventS.
Several definitions are moved inside the module to ensure it follows the
same order as FRP.Yampa.EventS, which makes ensuring consistency across
both packages easier.
@ivanperez-keera ivanperez-keera added this to the Dunai 0.12.2 milestone Feb 22, 2024
@ivanperez-keera ivanperez-keera self-assigned this Feb 22, 2024
ivanperez-keera added a commit that referenced this issue Feb 22, 2024
Several definitions are currently being defined in FRP.BearRiver that,
in Yampa, are instead defined in an internal module FRP.Yampa.Hybrid. To
make it easier to port code over from Yampa to bearriver, we decide to
move those definitions into a matching module FRP.BearRiver.Hybrid on
the bearriver side.

The module is currently incomplete. Not all definitions from
FRP.Yampa.Hybrid exist in FRP.BearRiver. This commit moves only those
definitions that currently are being exported by FRP.BearRiver, which
EventS will depend on.
ivanperez-keera added a commit that referenced this issue Feb 22, 2024
The module FRP.BearRiver.EventS does not contain all definitions offered
by its Yampa counterpart. This makes the interface offered by bearriver
not compliant with Yampa, therefore not delivering on the promise of
being API-compatible.

This commit adds missing definitions to the module FRP.BearRiver.EventS.
Several definitions are moved inside the module to ensure it follows the
same order as FRP.Yampa.EventS, which makes ensuring consistency across
both packages easier.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant