Marius Sarca

My 2 cents on this issue: the fact that someone knows how to write a validation schema doesn't mean they know how to use opis/json-schema. If you want to use...

> This is about "rights" now? > At that point, you can choose to meet the criteria or not. No doubt this is about rights! Your personal opinion is not...

You are opening issues regarding our library and then you declare *I am puzzled by you treating this as some sort of philosophical debate about subjectivity or some sort of...

Given the fact that our library passes all JSON Schema tests, the only issue left is the default configuration of the validator. We can not change that because of semantic...

My two cents on this issue: the heuristic nature of the parser should be preserved. It served us well for years and we all knew too well that there are...

@xepozz If you believe you have discovered a bug, please open a new issue so we could treat it properly. Also, you must be aware that Opis Closure 4.x is...

Just to be clear for everyone reading this thread: our public API consist of a single function `Opis\Closure\init`. Everything else is internal. Please use this library strictly for closure serialization/unserialization....

@xepozz Please open a new issue and provide the most basic example that can be reproduced. Thanks.

@xepozz I did take a look at your test results and the first thing that struck me was [this](https://github.com/yiisoft/composer-config-plugin/pull/82/checks?check_run_id=759176657#step:12:455): `Error: Class 'Environment\Serializer\CustomSerializer' not found`. Incidentally that is [the class](https://github.com/yiisoft/composer-config-plugin/pull/82/commits/8dedfe1d1e7047178e3543e804ca943b82d37047#diff-43a8d0faf6ba4f9a169c48ff56b19c18) where...

@mnapoli We are also dependant on `ext-tokenizer` #92, and nobody ever complained 😅. The FFI extension is a bundled extension, just like `ext-tokenizer`, `ext-pdo`, or `ext-mbstring`, and I don't think...