-
Notifications
You must be signed in to change notification settings - Fork 14
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
Feature/url extractor #558
Conversation
41ddc18
to
9601fc3
Compare
so we are avoiding a repository call, besides the node might have been deleted meanwhile also next id which was used for `NodeDeletedEvent` might be nil
that listens to change events of nodes
9601fc3
to
e0f3411
Compare
e0f3411
to
14cf422
Compare
Hey @electronicbites, regarding the topic:
when we have multiple outlines, how can we only subscribe (get updates for) the outline we are currently editing and not updates from other episode-nodes someone else is using in another episode? is this already the case or would the subscribe with episode_id be a good idea here? |
@sorax currently there is now way. It totally makes sense to create a channel per outline. I was about to write, we will do it later, but the more I am thinking about, I am about to revert this commit ... still thinking ;) |
let's merge this and do it later on |
Introduces a mechanism to detect URLs in node contents. If an URL is detected it just gets logged. It should be stored as an entity to the database. The frontend could present detected URls, the content of a website could be scraped and URLs can be exported to the show notes
This PR also introduces ChangesListener that subscribes to every change in the outliner.
The
EventConsumer
was renamed toCommandProcessor
episode_id was added to every event type while it was removed from the
Dispatch.subscribe
function since it was not used.