Skip to content
This repository was archived by the owner on Dec 5, 2024. It is now read-only.

Properly identifying GitRemote.Default #486

Merged
merged 1 commit into from
Dec 1, 2017
Merged

Conversation

StanleyGoldman
Copy link
Contributor

@StanleyGoldman StanleyGoldman commented Nov 30, 2017

Fixes #483

Changing how GitRemote.Default is defined.

Unity has issues serializing "NULL". For instance, null strings actually get serialized as empty.
We use a lot of structs.

In order to to help us identify a null struct, we use the Null Object Pattern.
Our default object for GitRemote was not correctly defined.
Some strings were null when they should be empty, in order to properly identify it as Default after deserialization.

@meaghanlewis
Copy link
Contributor

This LGTM 👍

After a domain reload strings are empty not null
Copy link

@drguthals drguthals left a comment

Choose a reason for hiding this comment

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

Can you add a couple of words as to why you are changing how gitRemote is defined?

@StanleyGoldman
Copy link
Contributor Author

Updated

@StanleyGoldman StanleyGoldman changed the title Preventing push before there is a remote Properly identifing GitRemote.Default Dec 1, 2017
@StanleyGoldman StanleyGoldman changed the title Properly identifing GitRemote.Default Properly identifying GitRemote.Default Dec 1, 2017
@StanleyGoldman StanleyGoldman merged commit 931f7c4 into master Dec 1, 2017
@StanleyGoldman StanleyGoldman deleted the fixes/empty-publish branch December 1, 2017 15:12
@StanleyGoldman StanleyGoldman restored the fixes/empty-publish branch December 1, 2017 19:48
@StanleyGoldman StanleyGoldman deleted the fixes/empty-publish branch December 1, 2017 20:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants