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
We now correctly report additional fields that contain an _ as long as the part that follows the _ doesn't conform to the format of a BCP 47 language tag. However, that's quite a wide range! @jpmckinney 's comment at OpenDataServices/cove#679 (comment) gives a clear example.
We should make the check smarter, such that if the first part before the _ isn't a field in the standard, we assume that it's an additional field and report on it.
The text was updated successfully, but these errors were encountered:
jpmckinney
changed the title
Additional Fields: Detect when a field is a field from the schema with a language suffix and don't report it as an additional field
Additional fields: Detect when a field is a field from the schema with a language suffix and don't report it as an additional field
Jul 7, 2023
jpmckinney
changed the title
Additional fields: Detect when a field is a field from the schema with a language suffix and don't report it as an additional field
Additional fields are under-reported: Check against schema, not just regex
Oct 24, 2024
In OpenDataServices/cove#679 we identified an issue with fields containing an
_
not being detected as additional fields.Functionally, this is identical to OpenDataServices/cove#402
We now correctly report additional fields that contain an
_
as long as the part that follows the_
doesn't conform to the format of a BCP 47 language tag. However, that's quite a wide range! @jpmckinney 's comment at OpenDataServices/cove#679 (comment) gives a clear example.We should make the check smarter, such that if the first part before the
_
isn't a field in the standard, we assume that it's an additional field and report on it.The text was updated successfully, but these errors were encountered: