ICRAR / ijson

100%

master: 100%

LAST BUILD ON BRANCH document-event-interception

branch: document-event-interception

CHANGE BRANCH

x

Reset

• document-event-interception
• async-fixes
• async-string-stream
• async_c
• bytes-prefix
• check-3.1.2.post0
• common_functions
• coros
• coverage-c
• coverage-increase
• decimal-c
• decoding-errors
• default_backend
• design_notes
• develop
• dump
• empty-members
• fixes-for-known-problems
• gh-actions
• ijson-dumps-multiple
• improved-readme
• issue-41
• issue-42
• issue-66
• items-and-kvitems-dont-join-path
• items_kwargs
• kvitems
• map_type
• master
• memory-leak
• more_tests
• new-devels
• no-tests-in-binary
• python-3.10
• python-parse-value-clarification
• python_multiple_values
• reader_conversion
• release-3.2.0
• rtobar-patch-1
• test
• test-comments
• test-module-rename
• test-wheels-on-travis
• toplevel_array
• travis-c-ext
• travis-more-python
• travis-xenial
• update-travis
• upload-check
• use_float
• v2.5
• v2.5.1
• v2.6.0
• v2.6.1
• v3.0
• v3.0.1
• v3.0.2
• v3.0.3
• v3.0.4
• v3.0rc1
• v3.0rc2
• v3.0rc3
• v3.1
• v3.1.1
• v3.1.2
• v3.1.2.post0
• v3.1.3
• v3.1.4
• v3.1.post0
• windows-wheels
• yajl109_test
• yajl2_c_parse_memleak
• zeros-python

Build # 267

Build Type

push

travis-ci-com

Committed by rtobar

Commit Message

State lack of event interception in async functions

The even interception mechanism currently works with the synchronous
generators and not with the async generators. The documentation doesn't
state this though, and has thus led to user confusion, like that
expressed in #48.

This commit adds a small statement to the documentation to clarify that
event interception currently works only with the synchronous generator
functions.

Signed-off-by: Rodrigo Tobar <rtobar@icrar.org>

Run Details

1476 of 1479 relevant lines covered (99.8%)

431.3 hits per line