Menu ▾ ▴

#21 unique ids of modulepropertytypes

0.1
closed
Jan Strauß
None
high
2015-02-16
2014-06-25
Ivan Bogicevic
No

There is no check whether an id of a modulepropertytype is already in use
-> When creating a new modulepropertytype or when renaming an existing one, the check has to search for existing modulepropertytype with the same name. If one exists, the new name is extended by a running number. e. g. "Author1". Additionaly, an infobox should inform the user "renamed modulepropertytype to X because Y already exists"

Discussion

  • Ivan Bogicevic

    Ivan Bogicevic - 2014-10-10
    • Milestone: 0.0.2 --> 0.1
     

  • Ivan Bogicevic

    Ivan Bogicevic - 2015-01-21
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,2 +1,2 @@
 There is no check whether an id of a modulepropertytype is already in use
--> When creating a new modulepropertytype or when renaming an existing one, the check has to block existing ids which already exist
+-> When creating a new modulepropertytype or when renaming an existing one, the check has to search for existing modulepropertytype with the same name. If one exists, the new name is extended by a running number. e. g. "Author1". Additionaly, an infobox should inform the user "renamed modulepropertytype to X because Y already exists"
    • Priority: --> high
     

  • Ivan Bogicevic

    Ivan Bogicevic - 2015-02-04
    • assigned_to: Jan Strauß
     

  • Ivan Bogicevic

    Ivan Bogicevic - 2015-02-16
    • status: open --> closed
     

  • Ivan Bogicevic

    Ivan Bogicevic - 2015-02-16

    Ok! (Solved with autorenaming, e. g. when "interface" already exists, the new name is "interface1")

     

Log in to post a comment.