You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that on the guide Event Object page, there are several properties listed in the Properties section for the Event object such as node, web, handled, etc. that have all been removed from the docs in this repo, but are still shown on the live documentation site. The changes shown in the linked diff are nearly 7 months old, so it seems that the documentation site hasn't been refreshed in quite a while.
I understand that the current docs are likely meant to represent V1 while V2 is underway, but it would be nice to have at least a way to view the current state of the V2 docs via the site.
I have a large number of documentation improvements I wanted to submit in a PR, but will likely hold off until the functionality to rebuild the docs site has been fixed/re-ran, or have been split off into separate pages on the site.
Describe the change
I noticed that on the guide Event Object page, there are several properties listed in the Properties section for the
Event
object such asnode
,web
,handled
, etc. that have all been removed from the docs in this repo, but are still shown on the live documentation site. The changes shown in the linked diff are nearly 7 months old, so it seems that the documentation site hasn't been refreshed in quite a while.I understand that the current docs are likely meant to represent V1 while V2 is underway, but it would be nice to have at least a way to view the current state of the V2 docs via the site.
I have a large number of documentation improvements I wanted to submit in a PR, but will likely hold off until the functionality to rebuild the docs site has been fixed/re-ran, or have been split off into separate pages on the site.
Let me know if I can support in any way.
URLs
https://h3.unjs.io/guide/event#properties
Additional information
The text was updated successfully, but these errors were encountered: