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.

Sign up for GitHub

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

Containment and pointer rules do not propagate properly from mixins #968

Closed
kecso opened this issue Apr 22, 2016 · 0 comments
Closed

Containment and pointer rules do not propagate properly from mixins #968

kecso opened this issue Apr 22, 2016 · 0 comments
Assignees
@kecso
Labels
Bug Core Major
Milestone
v1.7.2

Comments

@kecso
Copy link
Member

kecso commented Apr 22, 2016

Given the following scenario:

  • there is type A and type B, both are descendants of FCO
  • there is a type C, that can contain both A and B type elements
  • there are also type subA which is an instance of A
  • finally we also have a type mixB that is an instance of FCO but has B as mixin

In this setup, all the instances of A, B, subA, and mixB should be valid child of any instance of C. Right now, the mixB instances would be classified as invalid children of C.

The same stands for possible pointer targets.
@kecso kecso self-assigned this Apr 22, 2016
@kecso kecso added this to the v1.8.2 milestone Apr 22, 2016
kecso added a commit that referenced this issue Apr 22, 2016
@kecso
Fix naming issues.
3aeb136 
Fixes #968
kecso added a commit that referenced this issue Apr 22, 2016
@kecso
Fix naming issues.
994c532 
Fixes #968
@kecso kecso mentioned this issue Apr 22, 2016
Merged
kecso added a commit that referenced this issue Apr 25, 2016
@kecso
Fix naming issues.
c8b667b 
Fixes #968
pmeijer pushed a commit that referenced this issue Apr 25, 2016
@kecso
Refactoring of export import functionality regarding new project pack…
53ec764 
…age (#974)

* Moving import and export related functionality to storage util.
The export import functions of a rawJsonProject can be used from any source (and not just with the help of a worker)
Also fixes #961.

* Adds test for worker functions regarding refactor
Fixes #966 issue

* Fixed test collisions

* Fix naming issues.
Fixes #968

* Fix for updateLibrary if it is done with URL

* Fix review comments

* Fix function description of importProjectJson
pmeijer pushed a commit that referenced this issue Apr 25, 2016
@kecso
Refactoring of export import functionality regarding new project pack…
4126e68 
…age (#974)

* Moving import and export related functionality to storage util.
The export import functions of a rawJsonProject can be used from any source (and not just with the help of a worker)
Also fixes #961.

* Adds test for worker functions regarding refactor
Fixes #966 issue

* Fixed test collisions

* Fix naming issues.
Fixes #968

* Fix for updateLibrary if it is done with URL

* Fix review comments

* Fix function description of importProjectJson
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kecso kecso

Labels
Bug Core Major
Projects
None yet
Milestone
v1.7.2
Development

No branches or pull requests
2 participants
@kecso @pmeijer