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

Archiving and reopening of ad hoc needs acts unexpectedly #2633

Closed
sigpie opened this issue Jan 8, 2019 · 2 comments
Closed

Archiving and reopening of ad hoc needs acts unexpectedly #2633

sigpie opened this issue Jan 8, 2019 · 2 comments

Comments

@sigpie
Copy link
Contributor

sigpie commented Jan 8, 2019

If an ad hoc need is created to connect with a need and that need is archived or deleted, the ad hoc need continues to exist, while the connection to the removed need is deleted. If the remote need is reopened, no new connection is established. As ad hoc needs don't get matches, any ad hoc need for a removed need can only be closed, as no other interaction is possible.

The same state is reached by archiving and reopening the ad hoc need.

I'm not sure what the expected behaviour would be, maybe a new connection between the reopened need and the ad hoc need.

@quasarchimaere
Copy link
Contributor

i will move this to later, so we can figure out how to handle this gracefully
my thought in general:

  • we should avoid creating adhoc needs and just use these as edge cases -> we should supply reactionUseCases within our useCase definitions for example

@quasarchimaere
Copy link
Contributor

adhoc needs are not used/available anymore, the logic changed

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

No branches or pull requests

2 participants