Introduce and use NoCrossReferencingLexemeStatements

Unpublished Commit · Learn More

Not On Permanent Ref: This commit is not an ancestor of any permanent ref.
This commit no longer exists in the repository. It may have been part of a branch which was deleted.This commit has been deleted in the repository: it is no longer reachable from any branch, tag, or ref.


Introduce and use NoCrossReferencingLexemeStatements

The previous implementation of merge validation would not
catch references to lexemes or sub entities from a variety
of places, for example:

  • Lexeme statement reference snak -> lexeme form statement qualifer
  • and many more

This new attempt has come from discussion on and about Iaf0582870
which was created to add Sense support for merging Lexeme entities.

T198106 is the origional ticket with the origional BDD for this
decision. It has also been double checked with Lydia and the folks that
worked on NoCrossReferencingFormStatements that I am removing here.

This patch also introduced LexemeStatementEntityReferenceExtractor.

Bug: T203454
Bug: T198106
Change-Id: Ie56adf738cb8cf6f5013ff99da9b69fad4ddf9d5


AddshoreAuthored on Sep 5 2018, 3:22 PM

Commit No Longer Exists

This commit no longer exists in the repository.