Project

General

Profile

Actions

Feature #8101

closed

Filter loop prevention

Added by Chris Macmahon over 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
11/16/2017
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:

Description

When doing aliases, can we have a check if name = value and reject the change or at least show a warning?

Actions #1

Updated by Jim Pingle about 4 years ago

  • Target version changed from 2.4.3 to 2.4.4
Actions #2

Updated by Anonymous almost 4 years ago

  • Assignee set to Anonymous
Actions #3

Updated by Anonymous almost 4 years ago

  • Status changed from New to 13
Actions #4

Updated by Anonymous almost 4 years ago

  • Status changed from 13 to In Progress
Actions #5

Updated by Anonymous almost 4 years ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100
Actions #6

Updated by Vladimir Lind almost 4 years ago

  • Status changed from Feedback to Resolved

Got warning on 2.4.4-DEVELOPMENT (arm) built on Fri Aug 10 19:14:45 EDT 2018 when creating alias 'test_alias' with value 'test_alias':

The following input errors were detected:

Alias value cannot be the same as the alias name: `test_alias and test_alias`

Actions

Also available in: Atom PDF