Ticket #1064 (closed Defect: fixed)

Opened 5 years ago

Last modified 5 years ago

Editing a single assoc def changes assoc def order accidentally

Reported by: jri Owned by: jri
Priority: Major Milestone: Release 4.8.6
Component: DeepaMehta Standard Distribution Version: 4.8.5
Keywords: Cc: dgf, Malte, JuergeN, robert.schuster
Complexity: 3 Area:
Module: deepamehta-core

Description

Try this:

  1. Select an assoc def (= association) which is not at the parent type's last position
  2. Press Edit
  3. Press OK

When you now select a parent type instance you'll see that the corresponding field moved to the last position.
The field order has changed accidentally.

Change History

comment:1 Changed 5 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 5 years ago by Jörg Richter <jri@…>

In 3d3a36da8c5de637298a99115098d52b4e40adad/deepamehta:

Add Core test to illustrate #1064.

See #1064.

comment:3 Changed 5 years ago by Jörg Richter <jri@…>

In c8d53e8abc94bc98e7f359fae0f6dbbe9daac781/deepamehta:

Add set-custom-assoc-type test (#1064).

See #1064.

comment:4 Changed 5 years ago by Jörg Richter <jri@…>

In e6fb06837814f71e4d9d02734d5b1b34a7e34fed/deepamehta:

Core fix: edit assoc def does not change order.

See #1064.

comment:5 Changed 5 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.