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

Implement autocomplete and string parsing for config handling #3027

Merged
merged 4 commits into from
Sep 23, 2023

Conversation

benwoo1110
Copy link
Member

No description provided.

*
* @param <T> The type of the object to serialize and deserialize.
*/
public interface NodeSerializer<T> {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if there's benefit to breaking this into 2 separate functional interfaces for serialization and deserialization...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

well you cant really have a serialization without a deserialization

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was just thinking more for the fact that then they could be implemented with lambdas.

@benwoo1110 benwoo1110 merged commit 5845fdd into MV5 Sep 23, 2023
2 checks passed
@benwoo1110 benwoo1110 deleted the ben/mv5/config-suggest-parser branch September 23, 2023 01:39
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 this pull request may close these issues.

None yet

2 participants