Fix Swift sample for SignUpViewController fields

[richard4339]

The swift example was actually the Objective C sample. Modified it to be an array and changed the wording below to match the wording in the LogInViewController sample above.

[hramos]

The code update looks good, but the wording now only matches the Swift example. Think there's any wording we could use here that works for both?

[richard4339]

I was honestly thinking the same thing. Before I address that I'll ask
another question first: I assume it's JavaScript swapping the sample code
from objective c to swift; there isn't anything in place that will swap the
wording in the documentation anywhere is there? I haven't seen anything
like that, but I haven't read the entire thing in depth (nor have I found
the JavaScript that swaps it when viewing the source code).

If not, I'll just reword both to be an "if objective c ... if swift ..."
type sentence.

On Monday, August 22, 2016, Héctor Ramos [email protected] wrote:

The code update looks good, but the wording now only matches the Swift
example. Think there's any wording we could use here that works for both?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#368 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGJxCUQhKUT4o0PfuDoBvqO03h25l8sks5qiaEUgaJpZM4JpT1L
.

Richard
[email protected]

[hramos]

The code swapping is done in JavaScript, in main.js. It only toggles the code blocks, so the attached text should work for both. Perhaps this is a case where the code speaks for itself, and we don't need to point out Swift uses an array? The copy can just mention that one should pass the specific flags the login view controller should use.

[TomWFox]

It’s unfortunate that this has been dormant for so long. Would you either add two separate descriptions for swift and objective-c or remove the description entirely.

Alternatively you could add it as a comment in the code snippets.

If you make these changes (and resolve the conflict) I will happily merge this or pr the change myself.

[TomWFox]

I'm closing this now as I'm working on a PR to fix this an other syntax issues with the Parse UI docs.