[YANGTOOLS-850] PatternConstraint implementations are masking non-existent error-message Created: 21/Feb/18 Updated: 21/Feb/18 Resolved: 21/Feb/18 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | parser |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | 2.0.2 |
| Type: | Bug | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
When a pattern statement does not supply an error-message, we end up eagerly formatting a replacement message using the compiled java pattern. This ends up eating memory and also hurts the callers of getErrorMessage() – they are led to believe there is a model-supplied message, when there in fact is not. |
| Comments |
| Comment by Robert Varga [ 21/Feb/18 ] |