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

Rename OutputNote variants #586

Closed
hackaugusto opened this issue Apr 9, 2024 · 4 comments
Closed

Rename OutputNote variants #586

hackaugusto opened this issue Apr 9, 2024 · 4 comments
Assignees
Labels
refactoring Code clean-ups, improvements, and refactoring
Milestone

Comments

@hackaugusto
Copy link
Contributor

What should be done?

Rename Public to Full and Private to Minimal

How should it be done?

Straight forward renaming

When is this task done?

When the enum variants are renamed in the whole codebase

Additional context

#572 (comment)

@bobbinth
Copy link
Contributor

bobbinth commented Apr 9, 2024

This will actually be more than just renaming. After this the Full category will contain both public and private notes (and Minimal category will contain only private notes). So, we'll need to update the logic which sorts the notes into one group or the other. We will also need to convert all "full" private notes into "minimal" private notes when we built ProvenTransaction object from ExecutedTransaction.

@bobbinth bobbinth added the refactoring Code clean-ups, improvements, and refactoring label Apr 11, 2024
@bobbinth bobbinth added this to the v0.3 milestone Apr 11, 2024
@bobbinth
Copy link
Contributor

This is actually related to #496 - once this is resolved #496 should be resolved too.

@bobbinth
Copy link
Contributor

bobbinth commented May 6, 2024

@polydez - after my refactoring in #645, I think the variant names could be:

pub enum OutputNote {
    Full(Note),
    Header(NoteHeader),
}

Also, in your PR, it might make sense to make the refactoring I mentioned in #614 (comment) as @Dominik1999 is out today and he probably won't get to this until tomorrow.

@polydez polydez moved this from Todo to In Progress in User's testnet May 6, 2024
@polydez polydez moved this from In Progress to In Review in User's testnet May 8, 2024
@polydez
Copy link
Contributor

polydez commented May 8, 2024

Closed as resolved by #673

@polydez polydez closed this as completed May 8, 2024
@github-project-automation github-project-automation bot moved this from In Review to Done in User's testnet May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Code clean-ups, improvements, and refactoring
Projects
Status: Done
Development

No branches or pull requests

4 participants