Project

General

Profile

Feature #8101

Filter loop prevention

Added by Chris Macmahon over 2 years ago. Updated over 1 year ago.

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

100%

Estimated time:

Description

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

Associated revisions

Revision 169fad08 (diff)
Added by Stephen Jones over 1 year ago

Fixes #8101 added an input error if the alias name was equal to the alias value

History

#1 Updated by Jim Pingle almost 2 years ago

  • Target version changed from 2.4.3 to 2.4.4

#2 Updated by Anonymous over 1 year ago

  • Assignee set to Anonymous

#3 Updated by Anonymous over 1 year ago

  • Status changed from New to This Sprint

#4 Updated by Anonymous over 1 year ago

  • Status changed from This Sprint to In Progress

#5 Updated by Anonymous over 1 year ago

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

#6 Updated by Vladimir Lind over 1 year 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`

Also available in: Atom PDF