This repository has been archived by the owner on Jul 8, 2021. It is now read-only.
Add very basic "event" handling in Portal.js; Build sameAs on it #157
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Additionally replaces a few
indexOf
s withhas_hash
, fixes zombie posts hanging around and removes $rotonde from the Portals tab (those fixes could be separated and applied to master, but aren't critical).Portal now has got a basic
onparse
handler array, which should contain functions in the format of(json) => {...; return true / false;}
,true
meaning that the portal will be registered,false
meaning that the portal will be ignored.this
is the portal the handler's running against at the moment.The connection queue now accepts objects with
url
and optionaloncreate
andonparse
handlers.oncreate
allows settingis_remote = true;
early enough.