In example scripts make the credentials public or serialized fields

[mediumTaj]

Currently in all of the example files credentials are private member variables. We should convert these into either public variables or private serialized fields so we can access them in the inspector.

[mediumTaj]

@kimberlysiva Can you check this PR out for serialized credential, url and versionDates in the examples? #351

[kimberlysiva]

@mediumTaj This looks good, except there's a workspace id set in ExampleAssistant (probably want to remove that). Also if you set the fields in code they don't automatically get updated in the inspector, so now users will have to set things in the inspector. I think that's okay, but something to be aware of!

[mediumTaj]

Got it, i won't set any of the serialized fields in the example scripts and clear out the fields in the inspector.

[kimberlysiva]

Still, the thing to be aware of is that users can no longer just set the fields in code, they have to use the inspector. I was a bit surprised by that at first, but it makes sense when you realize that the sample objects are already serialized (and blank fields will be serialized values too). So users that are already setting things in code might be a bit confused! Also, I'm guessing this change will overwrite any credentials they've already set in code. You'll just need to add a note somewhere that users should now set credentials in the inspector.

Given all that, you might want to carefully consider this change. The videos probably show things being set in code, right?

[mediumTaj]

ah right, I didn't take into account the videos. Do you think having a note in the code to set all of these serialized fields in the inspector will take care of these cases? Something like

#region SET THESE VARIABLES IN THE INSPECTOR
[SerializeField]
private string _username;
[SerializeField]
private string _password;
[SerializeField]
private string _url;
#endregion

[kimberlysiva]

Great idea!

[mediumTaj]

OK Ill make that change