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

Rethink how we expose our dependencies to users #449

Closed
smelc opened this issue Feb 8, 2024 · 5 comments · Fixed by #448
Closed

Rethink how we expose our dependencies to users #449

smelc opened this issue Feb 8, 2024 · 5 comments · Fixed by #448

Comments

@smelc
Copy link
Contributor

smelc commented Feb 8, 2024

We need to discuss how we want to expose things on a module basis. We have strayed far from what was originally envisioned with the Cardano.Api and Cardano.Api.Shelley but I am partly to blame :).

Originally posted by @Jimbo4350 in #448 (review)

@carbolymer
Copy link
Contributor

What's the goal here, and what are expected improvements? The results of the discussion should definitely go to https://github.com/input-output-hk/cardano-node-wiki/wiki/Architecture-Decision-Records

This comment was marked as outdated.

@github-actions github-actions bot added the Stale label Mar 11, 2024
@smelc smelc removed the Stale label Mar 11, 2024

This comment was marked as off-topic.

@github-actions github-actions bot added the Stale label Apr 11, 2024
@smelc smelc removed the Stale label Apr 11, 2024
@carbolymer
Copy link
Contributor

This comment was marked as off-topic.

@github-actions github-actions bot added Stale and removed Stale labels May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants