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
Copy file name to clipboardexpand all lines: CHANGELOG.md
+21-66
Original file line number
Diff line number
Diff line change
@@ -6,85 +6,40 @@ In addition to bugfixes, this release introduces some minor breaking changes:
6
6
7
7
- Support for React Native 0.60+ only
8
8
- AndroidX support!
9
-
- Android & iOS package name have changed. If you rely on React Native
10
-
autolinking, you don't have to change a thing, otherwise, please see README to
11
-
update installation instruction.
12
-
- Permissions method names have changed for more explicit `checkPermissions` &
13
-
`requestPermissions`.
9
+
- Android & iOS package name have changed. If you rely on React Native autolinking, you don't have to change a thing, otherwise, please see README to update installation instruction.
10
+
- Permissions method names have changed for more explicit `checkPermissions` & `requestPermissions`.
14
11
- For iOS, we now avoid crashes at all cost, which means
15
-
- if a native method fails, it should be recoverable from JavaScript (promise
16
-
rejection) - we tried to cover most native code part in the bridge to be
17
-
able to catch all kind of exception
18
-
- An exception has been made for fetching event: if some part of the
19
-
serialization fails, a NSLog is emitted & the specific problematic part is
20
-
ommited (eg: an alarm or a structuredLocation could be missing) and the
21
-
process continues on other events. We keep in mind the idea of adding an
22
-
`error` field into calendar event so the information is explicitely
23
-
available from JavaScript. This is to avoid receving a promise rejection if
24
-
you fetch 2 months of events & have a single tiny information that we failed
25
-
to serialize. In this cases, you will receive all fetched calendar events
26
-
with just a tiny information missing, which offers a better UX.
12
+
- if a native method fails, it should be recoverable from JavaScript (promise rejection) - we tried to cover most native code part in the bridge to be able to catch all kind of exception
13
+
- An exception has been made for fetching event: if some part of the serialization fails, a NSLog is emitted & the specific problematic part is ommited (eg: an alarm or a structuredLocation could be missing) and the process continues on other events.
14
+
We keep in mind the idea of adding an `error` field into calendar event so the information is explicitely available from JavaScript.
15
+
This is to avoid receving a promise rejection if you fetch 2 months of events & have a single tiny information that we failed to serialize. In this cases, you will receive all fetched calendar events with just a tiny information missing, which offers a better UX.
27
16
28
17
### All platforms
29
18
30
-
- Added `removeCalendar` method
31
-
[#269](https://github.com/wmcmahan/react-native-calendar-events/pull/269) by
32
-
[@hmcheu](https://github.com/hmcheu)
19
+
- Added `removeCalendar` method [#269](https://github.com/wmcmahan/react-native-calendar-events/pull/269) by [@hmcheu](https://github.com/hmcheu)
33
20
34
21
### Android
35
22
36
-
- Package is now `com.calendarevents.RNCalendarEvents`
[#268](https://github.com/wmcmahan/react-native-calendar-events/pull/268) by
46
-
[@saghul](https://github.com/saghul)
47
-
- Added AndroidX support for react-native 0.60
48
-
[#263](https://github.com/wmcmahan/react-native-calendar-events/pull/263) by
49
-
[@yfuks](https://github.com/yfuks)
50
-
- Added: use PermissionListener to avoid Android manual steps
51
-
[#252](https://github.com/wmcmahan/react-native-calendar-events/pull/252) by
52
-
[@saghul](https://github.com/saghul)
53
-
- Added "NEVER ASK ME AGAIN" status added in Android
54
-
[#273](https://github.com/wmcmahan/react-native-calendar-events/pull/273) by
55
-
[@webtaculars](https://github.com/webtaculars)
56
-
- Added key to skip setting timezone on Android
57
-
[#271](https://github.com/wmcmahan/react-native-calendar-events/pull/271) by
58
-
[@eleddie](https://github.com/eleddie)
23
+
- Package is now `com.calendarevents.RNCalendarEvents`[a39efe7](https://github.com/wmcmahan/react-native-calendar-events/commit/a39efe79c730c578abe8614986d63520005a8e59) by [@MoOx](https://github.com/MoOx)
24
+
- Fixed `'boolean android.database.Cursor.moveToNext()' on a null object reference` error [e7c9680](https://github.com/wmcmahan/react-native-calendar-events/commit/e7c9680dd24a84229df234abf82277115d3f4f00) by [@MoOx](https://github.com/MoOx)
25
+
- Fixed parsing allowed availability [#268](https://github.com/wmcmahan/react-native-calendar-events/pull/268) by [@saghul](https://github.com/saghul)
26
+
- Added AndroidX support for react-native 0.60 [#263](https://github.com/wmcmahan/react-native-calendar-events/pull/263) by [@yfuks](https://github.com/yfuks)
27
+
- Added: use PermissionListener to avoid Android manual steps [#252](https://github.com/wmcmahan/react-native-calendar-events/pull/252) by [@saghul](https://github.com/saghul)
28
+
- Added "NEVER ASK ME AGAIN" status added in Android [#273](https://github.com/wmcmahan/react-native-calendar-events/pull/273) by [@webtaculars](https://github.com/webtaculars)
29
+
- Added key to skip setting timezone on Android [#271](https://github.com/wmcmahan/react-native-calendar-events/pull/271) by [@eleddie](https://github.com/eleddie)
[314](https://github.com/wmcmahan/react-native-calendar-events/pull/314) by
78
-
[@MoOx](https://github.com/MoOx)
33
+
- Package is now `RNCalendarEvents`[5ea007c](https://github.com/wmcmahan/react-native-calendar-events/commit/5ea007c0cbb147f37b7c1b748e6acae0a9485b88) by [@MoOx](https://github.com/MoOx)
34
+
- Fixed crashes related to structured location [#253](https://github.com/wmcmahan/react-native-calendar-events/pull/253) by [@eladgel](https://github.com/eladgel) & [4560a2f](https://github.com/wmcmahan/react-native-calendar-events/commit/4560a2ff883e1a8bad97ec16f3325d52ccccdff5) by [@MoOx](https://github.com/MoOx)
35
+
- Fixed iOS 13 show bug [#279](https://github.com/wmcmahan/react-native-calendar-events/pull/279) by [@huang303513](https://github.com/huang303513)
36
+
- Minimal version to iOS 9.0, like react-native 0.60 [5ea007c](https://github.com/wmcmahan/react-native-calendar-events/commit/5ea007c0cbb147f37b7c1b748e6acae0a9485b88) by [@MoOx](https://github.com/MoOx)
37
+
- Avoid iOS crashes at all cost [314](https://github.com/wmcmahan/react-native-calendar-events/pull/314) by [@MoOx](https://github.com/MoOx)
[#250](https://github.com/wmcmahan/react-native-calendar-events/pull/250) by
87
-
[@hugofelp](https://github.com/eladgel)
41
+
- Various minor README update [92c3238](https://github.com/wmcmahan/react-native-calendar-events/commit/92c3238eead14eb9a7d36398c3b9d17df0c9e270) by [@MoOx](https://github.com/MoOx)
42
+
- Updated docs with correct type for string dates [#250](https://github.com/wmcmahan/react-native-calendar-events/pull/250) by [@hugofelp](https://github.com/eladgel)
Copy file name to clipboardexpand all lines: CODE_OF_CONDUCT.md
+11-39
Original file line number
Diff line number
Diff line change
@@ -2,17 +2,11 @@
2
2
3
3
## Our Pledge
4
4
5
-
In the interest of fostering an open and welcoming environment, we as
6
-
contributors and maintainers pledge to making participation in our project and
7
-
our community a harassment-free experience for everyone, regardless of age, body
8
-
size, disability, ethnicity, gender identity and expression, level of
9
-
experience, nationality, personal appearance, race, religion, or sexual identity
10
-
and orientation.
5
+
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.
11
6
12
7
## Our Standards
13
8
14
-
Examples of behavior that contributes to creating a positive environment
15
-
include:
9
+
Examples of behavior that contributes to creating a positive environment include:
16
10
17
11
- Using welcoming and inclusive language
18
12
- Being respectful of differing viewpoints and experiences
@@ -22,53 +16,31 @@ include:
22
16
23
17
Examples of unacceptable behavior by participants include:
24
18
25
-
- The use of sexualized language or imagery and unwelcome sexual attention or
26
-
advances
19
+
- The use of sexualized language or imagery and unwelcome sexual attention or advances
27
20
- Trolling, insulting/derogatory comments, and personal or political attacks
28
21
- Public or private harassment
29
-
- Publishing others' private information, such as a physical or electronic
30
-
address, without explicit permission
31
-
- Other conduct which could reasonably be considered inappropriate in a
32
-
professional setting
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
33
24
34
25
## Our Responsibilities
35
26
36
-
Project maintainers are responsible for clarifying the standards of acceptable
37
-
behavior and are expected to take appropriate and fair corrective action in
38
-
response to any instances of unacceptable behavior.
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.
39
28
40
-
Project maintainers have the right and responsibility to remove, edit, or reject
41
-
comments, commits, code, wiki edits, issues, and other contributions that are
42
-
not aligned to this Code of Conduct, or to ban temporarily or permanently any
43
-
contributor for other behaviors that they deem inappropriate, threatening,
44
-
offensive, or harmful.
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.
45
30
46
31
## Scope
47
32
48
-
This Code of Conduct applies both within project spaces and in public spaces
49
-
when an individual is representing the project or its community. Examples of
50
-
representing a project or community include using an official project e-mail
51
-
address, posting via an official social media account, or acting as an appointed
52
-
representative at an online or offline event. Representation of a project may be
53
-
further defined and clarified by project maintainers.
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.
54
34
55
35
## Enforcement
56
36
57
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
-
reported by contacting the project team at [email protected]. The project
59
-
team will review and investigate all complaints, and will respond in a way that
60
-
it deems appropriate to the circumstances. The project team is obligated to
61
-
maintain confidentiality with regard to the reporter of an incident. Further
62
-
details of specific enforcement policies may be posted separately.
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.
63
38
64
-
Project maintainers who do not follow or enforce the Code of Conduct in good
65
-
faith may face temporary or permanent repercussions as determined by other
66
-
members of the project's leadership.
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.
67
40
68
41
## Attribution
69
42
70
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
71
-
version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
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]
Thank you for contributing! When contributing to this project, please first
4
-
discuss the change you wish to make via issue or any other method with the
5
-
owners of this repository before making a change.
3
+
Thank you for contributing! When contributing to this project, please first discuss the change you wish to make via issue or any other method with the owners of this repository before making a change.
6
4
7
-
Please note we have a code of conduct; follow it in all your interactions with
8
-
the project.
5
+
Please note we have a code of conduct; follow it in all your interactions with the project.
9
6
10
7
## Pull Request Process
11
8
12
-
1. Describe in detail the issue or feature and link to the issue that the pull
13
-
request aims to resolve.
14
-
2. If the pull request is a new feature, please ensure that there is parity
15
-
between iOS and Android. If not, please describe the reason.
16
-
3. Ensure that there are no compiler errors and that the changes are well vetted
17
-
in the run-time environment for iOS and Android.
9
+
1. Describe in detail the issue or feature and link to the issue that the pull request aims to resolve.
10
+
2. If the pull request is a new feature, please ensure that there is parity between iOS and Android. If not, please describe the reason.
11
+
3. Ensure that there are no compiler errors and that the changes are well vetted in the run-time environment for iOS and Android.
18
12
4. Remove any code that has been commented-out or used for debugging.
19
13
5. Update the README.md with details of changes to the api or install.
0 commit comments