-
Notifications
You must be signed in to change notification settings - Fork 0
Introduced SerializerBuilder and LanguageDeserializerBuilder #77
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
Conversation
Test Results3 017 tests 3 010 ✅ 3s ⏱️ Results for commit 1ca8ab6. ♻️ This comment has been updated with latest results. |
@@ -123,6 +123,9 @@ DynamicLanguage[] DeserializeExternalLanguage(LionWebVersions lionWebVersion, st | |||
SerializationChunk serializationChunk = | |||
JsonUtils.ReadJsonFromString<SerializationChunk>( | |||
File.ReadAllText($"chunks/externalDefs/{lionWebVersion.VersionString}/{name}.json")); | |||
return new LanguageDeserializer(lionWebVersion, compressedIdConfig: new(KeepOriginal: true)) | |||
return new LanguageDeserializerBuilder() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the advantage of using the Builder Pattern over using a configuration object (with reasonable effective defaults)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a question for @JojoEffect -- seems to be more C#-ish.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think one reason is that the Microsoft text editor can kinda handle auto-completion for methods, but mostly fails on anything more complex, like property initializers.
# Conflicts: # CHANGELOG.md
No description provided.