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

Generate warning when a before or after statement doesn't match any methods #410

Closed
Nava2 opened this Issue Aug 26, 2015 · 7 comments

Comments

@Nava2
Copy link
Member

commented Aug 26, 2015

Originally reported on Google Code with ID 512
Owned by tylerjdmcconnell


if I say

after junk {destuff();}

This is silently ignored. Junk could be mis-spelled and the user would never know.

There should be a warning.


Reported by @umple on 2014-02-11 16:48:59

@Nava2

This comment has been minimized.

Copy link
Member Author

commented Aug 26, 2015

Reported by tylerjdmcconnell on 2014-03-21 14:24:19

  • Owner changed: tylerjdmcconnell
@Nava2

This comment has been minimized.

Copy link
Member Author

commented Aug 26, 2015

The fix for this bug will exist in the code where the metamodel is fully populated.
Issue 403 is similar to this issue and the fix for it should give good guidance on
what to do for this issue.


Reported by tylerjdmcconnell on 2014-04-24 15:36:09

@vahdat-ab vahdat-ab assigned Shikib and unassigned aforward Jan 11, 2016

@vahdat-ab vahdat-ab added the ucosp label Jan 11, 2016

@TimLethbridge

This comment has been minimized.

Copy link
Member

commented Jan 13, 2016

Hint: Messages are listed in en.error. You would need to add a new one in a logical place in numeric sequence (close to other messages related to methods or before/after).

Try looking in UmpleInternalParser_CodeClass.ump There are lots of places where the warning-message method is called -- such as setFailedPosition(...)

@mkmicik

This comment has been minimized.

Copy link
Contributor

commented Jan 13, 2016

I can take this one.

Mike

Sent from my iPhone

On Jan 12, 2016, at 5:44 PM, TCLethbridge notifications@github.com wrote:

Hint: Messages are listed in en.error. You would need to add a new one in a logical place in numeric sequence (close to other messages related to methods or before/after).

Try looking in UmpleInternalParser_CodeClass.ump There are lots of places where the warning-message method is called -- such as setFailedPosition(...)


Reply to this email directly or view it on GitHub.

@vahdat-ab

This comment has been minimized.

Copy link
Member

commented Jan 13, 2016

Mike, Shikib has already started to work on this.
check ucosp.umple.org to see which issues have not been assigned.

@mkmicik

This comment has been minimized.

Copy link
Contributor

commented Jan 13, 2016

Whoops didn't notice that was a reply sorry.

Sent from my iPhone

On Jan 12, 2016, at 6:15 PM, Vahdat Abdelzad notifications@github.com wrote:

Mike, Shikib has already started to work on this.


Reply to this email directly or view it on GitHub.

@Shikib Shikib referenced this issue Jan 16, 2016

Merged

Issue410 #685

@TimLethbridge

This comment has been minimized.

Copy link
Member

commented Jan 24, 2016

See issue #686 This issue wasn't correctly fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.