You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6
+
7
+
## Our Standards
8
+
9
+
Examples of behavior that contributes to creating a positive environment include:
10
+
11
+
* Using welcoming and inclusive language
12
+
* Being respectful of differing viewpoints and experiences
13
+
* Gracefully accepting constructive criticism
14
+
* Focusing on what is best for the community
15
+
* Showing empathy towards other community members
16
+
17
+
Examples of unacceptable behavior by participants include:
18
+
19
+
* The use of sexualized language or imagery and unwelcome sexual attention or advances
20
+
* Trolling, insulting/derogatory comments, and personal or political attacks
21
+
* Public or private harassment
22
+
* Publishing others' private information, such as a physical or electronic address, without explicit permission
23
+
* Other conduct which could reasonably be considered inappropriate in a professional setting
24
+
25
+
## Our Responsibilities
26
+
27
+
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28
+
29
+
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30
+
31
+
## Scope
32
+
33
+
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34
+
35
+
## Enforcement
36
+
37
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38
+
39
+
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
40
+
41
+
## Attribution
42
+
43
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
We highly recommend you read through the [guide](http://docs.parseplatform.org/php/guide/) first. This will walk you through the basics of working with this sdk, as well as provide insight into how to best develop your project.
74
-
75
-
If want to know more about what makes the php sdk tick you can read our [API Reference](http://parseplatform.org/parse-php-sdk/namespaces/Parse.html) and flip through the code on [github](https://github.com/parse-community/parse-php-sdk/).
76
-
77
-
Http Clients
78
-
------------
114
+
### Http Clients
79
115
80
116
This SDK has the ability to change the underlying http client at your convenience.
81
117
The default is to use the curl http client if none is set, there is also a stream http client that can be used as well.
@@ -94,9 +130,7 @@ If you have a need for an additional http client you can request one by opening
94
130
95
131
If you wish to build one yourself make sure your http client implements ```ParseHttpable``` for it be compatible with the SDK. Once you have a working http client that enhances the SDK feel free to submit it in a PR so we can look into adding it in.
96
132
97
-
98
-
Alternate Certificate Authority File
99
-
------------------------------------
133
+
### Alternate CA File
100
134
101
135
It is possible that your local setup may not be able to verify with peers over SSL/TLS. This may especially be the case if you do not have control over your local installation, such as for shared hosting.
102
136
@@ -109,12 +143,16 @@ Once you have your bundle you can set it as follows:
We highly recommend you read through the [guide](http://docs.parseplatform.org/php/guide/) first. This will walk you through the basics of working with this sdk, as well as provide insight into how to best develop your project.
149
+
150
+
If want to know more about what makes the php sdk tick you can read our [API Reference](http://parseplatform.org/parse-php-sdk/namespaces/Parse.html) and flip through the code on [github](https://github.com/parse-community/parse-php-sdk/).
115
151
116
152
Check out the [Parse PHP Guide] for the full documentation.
117
153
154
+
### Use Declarations
155
+
118
156
Add the "use" declarations where you'll be using the classes. For all of the
119
157
sample code in this file:
120
158
@@ -130,9 +168,14 @@ use Parse\ParseAnalytics;
130
168
use Parse\ParseFile;
131
169
use Parse\ParseCloud;
132
170
use Parse\ParseClient;
171
+
use Parse\ParsePushStatus;
172
+
use Parse\ParseServerInfo;
133
173
```
134
174
135
-
Objects:
175
+
### Parse Objects
176
+
177
+
Parse Objects hold your data, can be saved, queried for, serialized and more!
178
+
Objects are at the core of this sdk, they allow you to persist your data from php without having to worry about any databasing code.
Queries allow you to recall objects that you've saved to parse-server.
257
+
Query methods and parameters allow allow a varying degree of querying for objects, from all objects of a class to objects created within a particular date range and more.
Persist files to parse-server and retrieve them at your convenience. Depending on how your server is setup there are a variety of storage options including mongodb, Amazon S3 and Google Cloud Storage. You can read more about that [here](https://github.com/parse-community/parse-server/#configuring-file-adapters).
Push notifications can be constructed and sent using this sdk. You can send pushes to predefined channels of devices, or send to a customized set of devices using the power of `ParseQuery`.
265
326
266
327
In order to use Push you must first configure a [working push configuration](http://docs.parseplatform.org/parse-server/guide/#push-notifications) in your parse server instance.
267
328
329
+
#### Push to Channels
330
+
331
+
You can send push notifications to any channels that you've created for your users.
332
+
268
333
```php
269
334
$data = array("alert" => "Hi!");
270
335
@@ -278,8 +343,13 @@ ParsePush::send(array(
278
343
"channels" => ["PHPFans"],
279
344
"data" => $data
280
345
), true);
346
+
```
347
+
348
+
#### Push with Query
281
349
350
+
You can also push to devices using queries targeting the `ParseInstallation` class.
282
351
352
+
```php
283
353
// Push to Query
284
354
$query = ParseInstallation::query();
285
355
$query->equalTo("design", "rad");
@@ -288,8 +358,14 @@ ParsePush::send(array(
288
358
"where" => $query,
289
359
"data" => $data
290
360
), true);
361
+
```
291
362
363
+
#### Push Status
292
364
365
+
If your server supports it you can extract and check the current status of your pushes.
366
+
This allows you to monitor the success of your pushes in real time.
As of April 5, 2017, Parse, LLC has transferred this code to the parse-community organization, and will no longer be contributing to or distributing this code.
0 commit comments