Project

General

Profile

Change Request #3468

Unify the emptyOrAlreadyExists in several aspects

Added by Anonymous about 2 years ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
07/03/2018
Due date:
% Done:

0%

Estimated time:

Description

The method emptyOrAlreadyExists is implemented in several classes.
Most of the implementation is identical for all classes. Differences are:
- string shown in the error message: this can either be unified as "Signal name is not valid" and "A Signal with this name already exists." or te string can be passed as arguments
- the local variable from which the getSignals() is called
The latter requires that all the types of those variables (at least MooNSolutionRequirementSpecification, ModeSpecification, FunctionalSpecification) extend ISignalsContainer.
This requires modifing the model so probably also creating a migrator (not sure if this is really the case)

History

#1 Updated by Johannes Eder over 1 year ago

  • Target version changed from AF3 2.14 RC1 (Feature Freeze) to Backlog

Also available in: Atom PDF