-
Notifications
You must be signed in to change notification settings - Fork 0
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
Sascha changelog 0.1.17-49 #78
Comments
Sadly overdue as of annoying bug issues that I could not resolve. The logic is already there. Fixed bug with 2b7ca93 and table gets correct preferred names from neo4j assigned. Plan |
Sorry, this is way too less information for me to have any solid idea. Let’s take a look at it later together.
Am 12. Dez. 2017, 00:02 +0100 schrieb SchSascha <notifications@github.com>:
… Sadly overdue as of annoying bug issues that I could not resolve. The logic is already there.
Fixed bug with 2b7ca93 and table gets correct preferred names from neo4j assigned.
As all the other widgets, e.g. Sankey widget are not modified, this issue remains open until further change is included that post-processes results once they are there.
I tried this already by modifying setEvents method in EventRetrievalResult class, yet this led to an error (null pointer). @khituras, any thoughts?
Plan
Once location is identified, I include the post-process such that it is available to all widgets once results are there.
This is resolved by tomorrow 12-12, or Wednesday 12-13 the latest.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
After discussion moved post processing for preferred names to service |
The text was updated successfully, but these errors were encountered: