Can be easily auto-corrected – just remove the reference
Less priority as it’s not being reported from a valid state
1504 and similar code(s):
Don’t need to be reported at all (even non-pubically) if nothing will occurr - I.e. if the one detected is exactly the same as the local/global
Add description for non-public modifications
Adding a local field causes issues in the validator when re-opening
TODO: when printing error/modification messages for entities, if field is local it must be located from the local fields collection, not the default scheme
Investigate what happens when custom/local field added...annotations made....custom field changes or is removed.
Things to check/future items:
Multiple segment tiers – any issues?
verify that dependent references or parents are within the same ST when required to be so....error if not. And then identify checks which should be ST isolated from each other, which should not be, and which it doesn’t matter.
This is meant to be a catch-all for any and all internal validation issues/bugs/necessities.
TBD
20003---Gloss {1384364445196237} had its DEPENDENT_HAND_ID and DEPENDENT_HAND_SHAPE_ID erased since the hand entity was deleted.---Public: False
20038 ---Removed 2347 dangling entities not referenced by any STATEMENT-FIELD.---Public: False
1st modification - dangling entities removed
2nd modification - if hand and handshape removed, remove dep_ids
should be independent.
erepr + " had dependent/corresponding gloss removed as the referenced gloss was deleted."
what was changed: why it was changed
erepr + " had a sign type value with no dependent sign type entity, so the sign type entity was created with that value."
why it was changed: what was changed
GD: actually currently there is only a modification for across tracks, within the same track remains only an error without a fix
GD: discuss more
I feel...
if something is deleted it should immediate be removed from everthting.
if something is added it should immediate be properlly added.
Otherwise these checks are not independent of each other.
Can be easily auto-corrected – just remove the reference
Less priority as it’s not being reported from a valid state
Don’t need to be reported at all (even non-pubically) if nothing will occurr - I.e. if the one detected is exactly the same as the local/global
TODO: when printing error/modification messages for entities, if field is local it must be located from the local fields collection, not the default scheme
Things to check/future items: