Noah Jackowitz

@jdesrosiers good point, the difference only occurs on failing instances - so this might not warrant a new keyword. That being said, when there are 100s of errors, it becomes...

@gregsdennis "foo" is not defined, because `anyOf` does not _require_ the failing subschema; the meaning of anyOf expects that it might not be that schema. It's more clear with this...

@jdesrosiers is right - this is only different from `unevaluatedProperties` on _failing_ instances, so it might not be worthwhile. In these cases, the difference is only that a property is...

I guess the most simple summary is that I think that all subschemas _applied_ by applicators should behave consistently with the current behavior of the `$ref` applicator. ## The Difference...

> Evaluated properties are defined as annotations. Ah - I realized this after I posted, thanks. > This is an issue with the validator you're using. Cool, I reported the...

> That's not actually how we use the term subschema. Oops! I'll use the term "applicable" to mean a subschema with relevant results regardless of validity. This is what I...

I'm on the fence about general rules for valid subschemas under invalid applicators. I think my general approach is that the instance _is_ whatever the passing subschema describes, even if...

Many of these issues show within a `TJ` operator with unusual character spacing -- but at least within `extraction_mode='plain'`, I wouldn't expect character spacing to be good reason to insert...

The other instance these issues appear is then an `Td` seems to do nothing. In this case it's a "new line" with 0 y offset and the x offset puts...

This is a relevant issue for my team. We are having an incredible amount of difficulty using `pip` on an internet-connected computer to download packages to transfer to an air-gapped...