-
Notifications
You must be signed in to change notification settings - Fork 147
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
Expose BlockLocator
#1762
Comments
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
This issue is extreamly easy. The goal of this issue is not to focus on understanding the structure of libplanet, but rather to follow the process of contributing to libplanet. |
Is the objective of this issue simply making the class [assembly: InternalsVisibleTo("Libplanet.Net")]
[assembly: InternalsVisibleTo("Libplanet.Net.Tests")] ? I'm asking because if it's the former it would be really simple, but in case of the latter, the members of the class |
Baby steps. 🙂 As the original #1760 (comment) suggest, the goal is eventually to decouple For now, I think just making partially mentioned entities |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
|
Currently Libplanet allows Libplanet.Net to see its internals in order to keep
BlockLocator
internal. However, it would be better if it is exposed as a public class instead.The text was updated successfully, but these errors were encountered: