Skip to content

Commit 902161e

Browse files
RodrigoSMarquesRodrigoSMarques
authored
Merge pull request #678 from ManasMalla/master
Update Readme.md to add info about supporting macOS platform
2 parents 149d250 + b0bddc6 commit 902161e

File tree

4 files changed

+117
-0
lines changed

4 files changed

+117
-0
lines changed

‎.github/ISSUE_TEMPLATE/---1-report-an-issue.md

+62
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
name: "\U0001F41B Report an issue"
3+
about: A feature is not working as expected.
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
### New Issue Checklist
11+
<!--
12+
Please check all of the following boxes [x] before submitting your issue.
13+
Click the "Preview" tab for better readability.
14+
Thanks for contributing to the Parse Flutter SDK!
15+
-->
16+
17+
- [ ] I am not disclosing a [vulnerability](https://github.com/parse-community/Parse-SDK-Flutter/security/policy).
18+
- [ ] I am not just asking a [question](https://github.com/parse-community/.github/blob/main/SUPPORT.md).
19+
- [ ] I have searched through [existing issues](https://github.com/parse-community/Parse-SDK-Flutter/issues?q=is%3Aissue).
20+
- [ ] I can reproduce the issue with the [latest version of the Parse Flutter SDK](https://github.com/parse-community/Parse-SDK-Flutter/releases). <!-- We don't investigate issues for outdated releases. -->
21+
- [ ] I can reproduce the issue with the [latest version of Parse Server](https://github.com/parse-community/parse-server/releases).
22+
23+
### Issue Description
24+
<!-- What is the specific issue? -->
25+
26+
### Steps to reproduce
27+
<!-- How can someone else reproduce the issue? -->
28+
29+
### Actual Outcome
30+
<!-- What outcome, for example query result, did you get? -->
31+
32+
### Expected Outcome
33+
<!-- What outcome, for example query result, did you expect? -->
34+
35+
### Pull Request
36+
<!--
37+
Check one of the following boxes [x] if you added a PR and add the link.
38+
If you need any guidance please do ask.
39+
-->
40+
41+
- [ ] 🤩 I submitted a PR with a fix.
42+
43+
### Environment
44+
<!-- Be specific with versions, don't use "latest" or semver ranges like "~x.y.z" or "^x.y.z". -->
45+
46+
Parse Flutter SDK
47+
- SDK version: `FILL_THIS_OUT`
48+
- Operating system: `FILL_THIS_OUT`
49+
- Operating system version: `FILL_THIS_OUT`
50+
51+
Server
52+
- Parse Server version: `FILL_THIS_OUT`
53+
- Operating system: `FILL_THIS_OUT`
54+
- Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): `FILL_THIS_OUT`
55+
56+
Database
57+
- System (MongoDB or Postgres): `FILL_THIS_OUT`
58+
- Database version: `FILL_THIS_OUT`
59+
- Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): `FILL_THIS_OUT`
60+
61+
### Logs
62+
<!-- Include relevant logs here. -->

‎.github/ISSUE_TEMPLATE/---2-feature-request.md

+34
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
name: "\U0001F4A1 Request a feature"
3+
about: Suggest new functionality or an enhancement of existing functionality.
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
### New Feature / Enhancement Checklist
11+
<!--
12+
Check all of the following boxes [x] before submitting your issue.
13+
Click the "Preview" tab for better readability.
14+
Thanks for contributing to the Parse Android SDK!
15+
-->
16+
17+
- [ ] I am not disclosing a [vulnerability](https://github.com/parse-community/Parse-SDK-Flutter/security/policy).
18+
- [ ] I am not just asking a [question](https://github.com/parse-community/.github/blob/main/SUPPORT.md).
19+
- [ ] I have searched through [existing issues](https://github.com/parse-community/Parse-SDK-Flutter/issues?q=is%3Aissue).
20+
21+
### Current Limitation
22+
<!-- Which current limitation is the feature or enhancement addressing? -->
23+
24+
### Feature / Enhancement Description
25+
<!-- What is the concept of the functionality and how should it be implemented? -->
26+
27+
### Example Use Case
28+
<!-- What is an example use case in steps (1. / 2. / 3. / etc.) that describes the functionality? -->
29+
30+
### Alternatives / Workarounds
31+
<!-- Which alternatives or workarounds exist currently? -->
32+
33+
### 3rd Party References
34+
<!-- Have you seen a similar functionality provided somewhere else? -->

‎.github/ISSUE_TEMPLATE/config.yml

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: 🙋🏽‍♀️ Getting help with code
4+
url: https://stackoverflow.com/questions/tagged/parse-platform
5+
about: Get help with code-level questions on Stack Overflow.
6+
- name: 🙋 Getting general help
7+
url: https://community.parseplatform.org
8+
about: Get help with other questions on our Community Forum.

‎packages/flutter/README.md

+13
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,19 @@ Due to Cross-origin resource sharing (CORS) restrictions, this requires adding `
5252
When running directly via docker, set the env var `PARSE_SERVER_ALLOW_HEADERS=X-Parse-Installation-Id`.
5353
When running via express, set [ParseServerOptions](https://parseplatform.org/parse-server/api/master/ParseServerOptions.html) `allowHeaders: ['X-Parse-Installation-Id']`.
5454

55+
#### Desktop Support (macOS)
56+
Due to security entitlements posed by the macOS framework, connecting to the Web and sharing data requires adding the following lines to code :
57+
```
58+
<key>com.apple.security.network.client</key>
59+
<true/>
60+
```
61+
to the following files:
62+
```
63+
/macOS/Runner/Release.entitlements
64+
/macOS/Runner/DebugProfile.entitlements
65+
```
66+
to help the Parse SDK for Flutter communicate with the Web to access the server and send/retrive data.
67+
5568
#### Network client
5669
By default, this SDK uses the `ParseHTTPClient`.
5770
Another option is use `ParseDioClient`. This client supports the most features (for example a progress callback at the file upload), but a benchmark has shown, that dio is slower than http on web.

0 commit comments

Comments
 (0)