[YANGTOOLS-1317] Remove UnknownStatement.getExtensionDefinition() Created: 06/Sep/21  Updated: 15/Oct/21  Resolved: 15/Oct/21

Status: Resolved
Project: yangtools
Component/s: model-api
Affects Version/s: None
Fix Version/s: 8.0.0

Type: Improvement Priority: Medium
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: pt
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Relates
relates to YANGTOOLS-1196 Do not generate EffectiveStatements f... Resolved
Sub-Tasks:
Key
Summary
Type
Status
Assignee
YANGTOOLS-1318 Remove RecursiveObjectLeaker Sub-task Resolved Robert Varga  
YANGTOOLS-1319 Deprecate UnknownSchemaNode.getExtens... Sub-task Resolved Robert Varga  

 Description   

UnknownSchemaNode has an unfortunate design flaw, where it can recursively refer to itself if there are other UnknownSchemaNode in its ExtensionDefinition (and those use that statement).

YANGTOOLS-1196 effectively eliminated this use case from our codebase, as we do not support any extensions which would have such interdependencies, but there are such extensions out there and those cannot be reasonably implemented now.

The crux of the problem is UnknownSchemaNode.getExtensionDefinition(), which is not really useful, as we already have the corresponding QName and the extension can easily be looked up from EffectiveModelContext. Remove this method.


Generated at Wed Feb 07 20:55:48 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.