Remove LSL-specific state machine events from SLua documentation #8
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.
SLua uses a different event model than LSL and does not support LSL's state machine. The events
state_entryandstate_exitare LSL-specific and should not appear in SLua reference documentation. Thetimerevent is supported in SLua and has been retained.Changes
scripts/generate-docs.js: AddedlslOnlyEventsfilter to skip state machine events (state_entryandstate_exit) during SLua documentation generationstate_entry.mdxandstate_exit.mdxfromsrc/content/docs/script/slua-reference/events/timer.mdxin SLua documentation as this event is supportedLSL documentation retains all 43 events. SLua documentation now correctly shows 41 events (excluding only
state_entryandstate_exit).Original prompt
<issue_description>SLua does not use LSL's state machine model. The state_entry and state_exit events are LSL-specific and should likely be removed from the SLua reference documentation.
Possible solution:
state_entry,state_exitandtimerevents when generating SLua event pages using generate-docs.jsComments on the Issue (you are @copilot in this section)
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.