<!--
Set the PR title to a meaningful commit message in imperative form. E.g.:
linting: Print line and column number of violation (fixes #999).
-->
The changes in this PR are only to facilita...
> re: title I think the current title is better. I think adding `StructuredIrStreamReader` to the title is too much detail for someone not familiar with code. Maybe `feat(structured): Add support f...
Sorry for the confusion. I mean we want to add this at https://github.com/y-scope/clp-ffi-js/blob/d2556b2fb6d986182b247c660244dfbc923e37ea/src/clp_ffi_js/ir/StreamReader.hpp#L99
```
@throw ClpFfi...
The suggested wording was from the Coding Guidelines. Might be good to keep that for consistency: https://www.notion.so/yscope/WIP-Coding-Guidelines-9a308b847a5343958ba3cb97a850be66?pvs=4#13504e4d9...
Added some comments about documentation for the exception behaviour
For the PR title, how about
```
feat(StructuredIrStreamReader): Add support for log-level filtering.
```
Sorry for the lack of context at https://github.com/y-scope/clp-ffi-js/pull/35#discussion_r1888811976
```suggestion
* @return See `decode_range`.
* @throw Propagates `ToStringFunc`'...
Since the structured one also throws the same error when a message cannot be decoded, let's document this `@throw` in the docstring at https://github.com/y-scope/clp-ffi-js/blob/d2556b2fb6d986182b2...
Added some comments about documentation for the exception behaviour
For the PR title, how about
```
feat(StructuredIrStreamReader): Add support for log-level filtering.
```
Added some comments about documentation for the exception behaviour
For the PR title, how about
```
feat(StructuredIrStreamReader): Add support for log-level filtering.
```
tested with a clp-ffi-py generated IRv2 file with various log levels. all good except
1. logs can be printed before returning null in `auto StreamReader::generic_decode_range`: https://github.com/...