-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Document or remove any event that can be fired by "Map" #2232
Comments
The biggest offender is |
I'd be fine with publicly documenting |
Agree with @jfirebaugh, if an event isn't public, we shouldn't emit it. |
👍 Makes sense. I adjusted the issue title to reflect this approach. |
Here is a list of all of the events that are undocumented and where they live in the code. Some of them may be undocumented intentionally and the link I put here may not be the canonical link. Tell me which should be documented and which should be removed!
|
Wow thanks @lyzidiamond! I can help with this.. I just added the |
@bhousel ah yes, i saw the doc comments in the code and was confused as to why they weren't showing in the docs! Comment above updated. |
@bhousel also I'm happy to add the doc, just need to know which ones to document! |
A bunch more here, including the Lines 508 to 527 in 2028b48
|
As somebody who did some ol3, I was actually looking for map generated events and was wondering if there were any because they are not in listed in the API documentation. In particular, I was looking for an event which is fired whenever a render is completed. map#render seems to fit. It would be great if these events could be documented, even if very briefly. Otherwise adopters will just try to find them in the code. Even a list of available events without documentation (such as above) is very helpful. |
@lucaswoj @bhousel @jfirebaugh any idea which of the events i listed should have doc and which should be removed? Happy to hit this once I know which is which. |
Of the events listed, I think we should document |
I think these should all be documented except for |
I think we should clean up our events architecture by doing the following things: Already Done
Step 1
Step 2
Step 3
Step 4
|
Revisiting this at a high level. Now that #3244 has landed we have better visibility into our events: Events fired in GL JS
Events Documented in GL JS
Events Fired but not Documented
Events to be Merged into the
|
There are many events that we fire but don't consider part of our public API. Many users are using these events despite them being undocumented. We should consider prefixing these events with an
_
, like a private method, to discourage their use.The text was updated successfully, but these errors were encountered: