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

Squash from #41, Solved conflicts on notification codes; #58

Closed
wants to merge 6 commits into from
Closed

Squash from #41, Solved conflicts on notification codes; #58

wants to merge 6 commits into from

Conversation

Lucashuang0802
Copy link

Link #21 and #41

@nlutsenko nlutsenko self-assigned this May 21, 2015
@Lucashuang0802 Lucashuang0802 changed the title Squash from #41, some notification codes are conflict; Squash from #41, Solved conflicts on notification codes; May 21, 2015
@nlutsenko
Copy link
Contributor

@Lucashuang0802 Sorry, took me a while to get back to you.
Can you rebase the commit on master so it's mergeable?

@Lucashuang0802
Copy link
Author

Sure, I will take some time to rebase it and fix it tonight.

@nlutsenko
Copy link
Contributor

@Lucashuang0802 Awesome, thank you! Everything else looks great!

@Lucashuang0802
Copy link
Author

Okay, I will comment it once I am done with it.

Lucashuang0802 added 2 commits May 27, 2015 21:14
Conflicts:
	en/ios/handling-errors.mdown
	en/ios/in-app-purchases.mdown
	en/ios/local-datastore.mdown
	en/ios/push-notifications.mdown
	en/ios/queries.mdown
	en/ios/user-interface.mdown
@Lucashuang0802
Copy link
Author

Finished the type fixes and rebase. Code can be merged to the master branch right now. Deleted some help-wanting indicator from Swift docs.

@nlutsenko
Copy link
Contributor

Perfect! Ready to merge in!
One last thing, could you squash all these things together so it's 1 commit?
This helps us keep the repo history clean, as merge branch master into swift-ios-update is not really helpful when you look at the history... :)

LucashuangGZ0802 added 3 commits May 28, 2015 09:51
Fixed typo

Small grammar and style fixes.

Actualization documentation

Update of russian version of documentation based on english version.

Add Promises section to the JS Guide.

Make it clearer that Promises is the way to go with JS.

Change incorrect string concatenation character

In the very first PHP code example, the string concat character is given as "+" in the code. It should be "." I think this is critical, because most users might copy-paste the first example and might get "0" if there was an exception, instead of the actual message.

Fix Links in Performance Guide

Also fixes bug when Swift is selected, since there are no Swift examples for these yet.

Facebook SDK Integration clarification

The Parse SDK does not automatically fetch Facebook data based on the read p

this was a typo

As evidenced by the same sentence later in the parse website (where I read this document) the line should read "just by" and not "just be".

Clarify subclassing instructions and difference between +load and +initialize.

Update objects.mdown

Fix typo in REST reference section

Fix spacing

get rid of ��

Remove ��

Minor grammar corrections in the Facebook user section.
…Docs into swift-ios-update

# By Hector Ramos (4) and others
# Via Héctor Ramos (9) and others
* 'swift-ios-update' of https://github.com/Lucashuang0802/Docs:
  Minor grammar corrections in the Facebook user section.
  Fixed typo
  Remove ��
  get rid of ��
  Fix spacing
  Fix typo in REST reference section
  Update objects.mdown
  Add link to open Swift samples issue.
  this was a typo
  Clarify subclassing instructions and difference between +load and +initialize.
  Fix Links in Performance Guide
  Change incorrect string concatenation character
  Make it clearer that Promises is the way to go with JS.
  Add Promises section to the JS Guide.
  Squash from #41, some notification codes are conflict;
  Actualization documentation
  Small grammar and style fixes.
  Facebook SDK Integration clarification
@Lucashuang0802
Copy link
Author

I will just create another pull request and I will delete the previous after merging. That's more easier.

@Lucashuang0802
Copy link
Author

Link #73

@nlutsenko
Copy link
Contributor

Superseeded by #73

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