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

Shallow References in Many-To-One (Single Edge) vs One-To-Many / Many-To-Many (Multi-Edge) #528

Closed
dimitarp opened this issue Mar 27, 2017 · 2 comments
Labels
contribution wanted this feature is wanted but won't be implemented by core team due to limited resources Core Team This issue will be implemented by JaVers core team fixed good first issue

Comments

@dimitarp
Copy link

Why shallow references are considered when building single edges but not multi-edges?
Is this a bug or am I missing something?

Thanks in advance!

@bartoszwalacik
Copy link
Member

bartoszwalacik commented Mar 29, 2017

Looks like a missing feature,
ideal for contribution

@bartoszwalacik bartoszwalacik added the Core Team This issue will be implemented by JaVers core team label Feb 12, 2019
FmeuMan added a commit to FmeuMan/javers that referenced this issue Mar 11, 2019
FmeuMan added a commit to FmeuMan/javers that referenced this issue Mar 12, 2019
FmeuMan added a commit to FmeuMan/javers that referenced this issue Mar 12, 2019
FmeuMan added a commit to FmeuMan/javers that referenced this issue Mar 12, 2019
FmeuMan added a commit to FmeuMan/javers that referenced this issue Mar 12, 2019
bartoszwalacik added a commit that referenced this issue Mar 14, 2019
@bartoszwalacik bartoszwalacik added contribution wanted this feature is wanted but won't be implemented by core team due to limited resources fixed - waiting to be released fixed and removed fixed - waiting to be released labels Mar 15, 2019
@bartoszwalacik
Copy link
Member

fix is released in 5.3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution wanted this feature is wanted but won't be implemented by core team due to limited resources Core Team This issue will be implemented by JaVers core team fixed good first issue
Projects
None yet
Development

No branches or pull requests

2 participants