Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Duplicate elements in a class should raise an error #172

Closed
Nava2 opened this issue Aug 26, 2015 · 14 comments
Closed

Duplicate elements in a class should raise an error #172

Nava2 opened this issue Aug 26, 2015 · 14 comments
Assignees
@aforward
Labels
Component-Metamodel Diffic-Easy Should be obvious how to fix it and doable in less than a week by an experienced Umple developer Priority-High This problem or enhancement is likely to be highly visible and or impactful of users Type-Defect ucosp Suitable for 4th year capstone projects

Comments

@Nava2
Copy link
Contributor

Nava2 commented Aug 26, 2015

Originally reported on Google Code with ID 272
Owned by bjquebecdesloges

An error message should be returned when you enter code such as:

class X {
a;
a;
}

This should report a new error code to be added to en.error

Similar messages should result whenever an association name would clash with an existing
attribute or association.

Note: In UmpleOnline, there should also be a mechanism to detect duplicates when they
are being edited in the diagram.

Reported by @umple on 2012-02-07 23:30:00
@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

Reported by @umple on 2012-02-15 17:31:41

  • Labels added: Component-Metamodel

@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

Reported by @umple on 2012-06-14 15:32:35

  • Labels added: Diffic-Easy

@Nava2 Nava2 added Type-Defect Priority-High This problem or enhancement is likely to be highly visible and or impactful of users Component-Metamodel Status-Fixed Diffic-Easy Should be obvious how to fix it and doable in less than a week by an experienced Umple developer ucosp Suitable for 4th year capstone projects labels Aug 26, 2015
@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

See also issue 159

Reported by @umple on 2012-06-15 15:22:06

@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

Reported by @umple on 2012-09-27 18:56:08

  • Owner changed: christopher.hogan49
  • cc added: +@umple

@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

See also issue 188 - duplicate associations

Reported by @umple on 2012-09-27 20:30:40

@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

Error message for this will be 22 - for duplicate attribites and 23 - for attributes
that would result in duplicates of associations e.g.

class C {
a;

  • -- 1 A;
    bs;
    1 -- * B;
    }

class A {}
class B {}

Reported by @umple on 2012-09-28 19:24:01

@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

Reported by @umple on 2012-09-29 14:57:24

  • Labels added: ucosp

@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

Reported by @umple on 2012-12-11 13:07:46

  • Status changed: Fixed

@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

I just discovered that this issue was never completed. Error 23 is not generated in
cases where an association name clashes with an attribute name.

Reported by @umple on 2012-12-18 22:32:59

  • Status changed: MostlyDone

@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

This issue remains a UCOSP issue that could be a good starter problem.

Reported by @umple on 2012-12-31 13:30:42

  • Owner removed
  • Labels added: Priority-High
  • Labels removed: Priority-Medium

@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

See also issue 253 which should be done together with this one

Reported by @umple on 2012-12-31 17:46:39

@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

Reported by @umple on 2013-01-19 17:05:24

  • Owner changed: bjquebecdesloges

@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

I have submitted a patch to for covering the case where an association name clashes
with an attribute name so this issue should be complete now.

Reported by bjquebecdesloges on 2013-02-05 16:16:11

@Nava2
Copy link
Contributor Author

Nava2 commented Aug 26, 2015

Reported by @umple on 2013-02-05 17:23:28

  • Status changed: Fixed

@Nava2 Nava2 closed this as completed Aug 26, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aforward aforward

Labels
Component-Metamodel Diffic-Easy Should be obvious how to fix it and doable in less than a week by an experienced Umple developer Priority-High This problem or enhancement is likely to be highly visible and or impactful of users Type-Defect ucosp Suitable for 4th year capstone projects
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aforward @Nava2