A defined key in a trait is not recognized by the classes that use the trait #1029

Open
ahmedvc opened this Issue Mar 30, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@ahmedvc
Contributor

ahmedvc commented Mar 30, 2017

Try the model below. Id will not be recognised as a key in the generated code.
trait API{
id;
key {id}
}

class Test{
isA API;
}

@vahdat-ab vahdat-ab self-assigned this Mar 30, 2017

@vahdat-ab

This comment has been minimized.

Show comment
Hide comment
@vahdat-ab

vahdat-ab Mar 31, 2017

Member

@ahmedvc I hope you don't need this feature as an essential part of your work.
It's a little bit tricky because it's been implemented in that way for classes so it becomes hard to transfer it easily to traits. I need to refactor the code to get it working.

Member

vahdat-ab commented Mar 31, 2017

@ahmedvc I hope you don't need this feature as an essential part of your work.
It's a little bit tricky because it's been implemented in that way for classes so it becomes hard to transfer it easily to traits. I need to refactor the code to get it working.

@ahmedvc

This comment has been minimized.

Show comment
Hide comment
@ahmedvc

ahmedvc Mar 31, 2017

Contributor

No. It's not relevant to my work. I was testing traits in C++ when I found the issue. It is low priority for now.

Contributor

ahmedvc commented Mar 31, 2017

No. It's not relevant to my work. I was testing traits in C++ when I found the issue. It is low priority for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment