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
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -198,7 +198,7 @@ Additionally, direct `DAVClient()` instantiation should migrate to `get_davclien
198
198
199
199
### Changed
200
200
* Optimilizations on data conversions in the `CalendarObjectResource` properties (https://github.com/python-caldav/caldav/issues/613 )
201
-
* Lazy imports (PEP 562) -- `import caldav` is now significantly faster. Heavy dependencies (lxml, niquests, icalendar) are deferred until first use. https://github.com/python-caldav/caldav/pull/621
201
+
* Lazy imports (PEP 562) -- `import caldav` is now significantly faster. Heavy dependencies (lxml, niquests, icalendar) are deferred until first use. https://github.com/python-caldav/caldav/issues/621
202
202
* Search refactored to use generator-based Sans-I/O pattern -- `_search_impl` yields `(SearchAction, data)` tuples consumed by sync or async wrappers
203
203
* Configuration system expanded: `get_connection_params()` provides unified config discovery with clear priority (explicit params > test server config > env vars > config file)
204
204
* `${VAR}` and `${VAR:-default}` environment variable expansion in config values
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ The `compatibility_hints.py` has been moved from the test directory to the codeb
25
25
26
26
This is not set in stone. If you feel strongly for using something else, use something else in the commit message and update this file in the same commit.
27
27
28
-
"Imperative mood" is to be used in commit messages.
28
+
"Imperative presens" or "imperative mood" is to be used in commit messages.
29
29
30
30
The boundaries of breaking changes vs "non-breaking" changes [may be blurry](https://xkcd.com/1172/). In the CHANGELOG I've used the concept "potentially breaking changes" for things that most likely won't break anything for anyone. Potentially breaking changes should be marked with `!` in the commit header. Breaking changes should be marked both with `!` and `BREAKING CHANGE:`
31
31
@@ -62,11 +62,9 @@ Consider this procedures to be a more of a guideline than a rigid procedure. Us
62
62
63
63
* Write up your changes
64
64
65
-
* Run `pytest` for a quick run of the tests. They should still pass.
65
+
* Run `pytest`. The tests should still pass. (Beware: tests may take very long time to run and may consume a lot of memory and disk space if the tests have the permissions to start docker containers).
66
66
67
-
* Run `tox -e style` to verify a consistent code style (this may modify your code).
68
-
69
-
* Consider to write some lines in the documentation and/or examples covering your change
67
+
* Consider to write some lines in the documentation, changelog and/or examples covering your change
0 commit comments