Skip to content

docs: update Events.md to include frontend/mobile startup events - #10854

Open
tmzhuang wants to merge 3 commits into
TriliumNext:mainfrom
tmzhuang:docs/10853-run-events
Open

docs: update Events.md to include frontend/mobile startup events#10854
tmzhuang wants to merge 3 commits into
TriliumNext:mainfrom
tmzhuang:docs/10853-run-events

Conversation

@tmzhuang

@tmzhuang tmzhuang commented Aug 4, 2026

Copy link
Copy Markdown
  • Converted HTML table to Markdown table for better readability
  • Added missing frontendStartup and mobileStartup event values
  • Clarified that run event values are mutually exclusive
  • Added note about creating multiple script copies for multiple triggers
  • Fixed missing newline at end of file

Closes #10853

- Converted HTML table to Markdown table for better readability
- Added missing `frontendStartup` and `mobileStartup` event values
- Clarified that `run` event values are mutually exclusive
- Added note about creating multiple script copies for multiple triggers
- Fixed missing newline at end of file

Closes TriliumNext#10853
@dosubot dosubot Bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Aug 4, 2026
@tmzhuang

tmzhuang commented Aug 4, 2026

Copy link
Copy Markdown
Author

I'm not 100% sure about the relative link to the mobile frontend docs. I calculated it based on the url on the production docs.

@greptile-apps

greptile-apps Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

The PR converts the backend-script events table to Markdown and documents frontend and mobile startup triggers.

  • Adds frontendStartup and mobileStartup event descriptions.
  • Clarifies the descriptions for scheduled backend events and instance restrictions.
  • Adds the missing final newline.

Confidence Score: 4/5

The PR should not merge until the outstanding incorrect guidance about combining multiple run values is corrected.

The current documentation says event values are mutually exclusive and requires separate script copies, while backend, frontend, and mobile event handlers independently retrieve scripts matching each run value, so one script note can validly carry and respond to multiple values.

Files Needing Attention: docs/User Guide/User Guide/Scripting/Backend scripts/Events.md

Important Files Changed

Filename Overview
docs/User Guide/User Guide/Scripting/Backend scripts/Events.md Converts the events reference to Markdown and expands its startup-event documentation.

Reviews (3): Last reviewed commit: "Merge branch 'main' into docs/10853-run-..." | Re-trigger Greptile

</tbody>
</table>

| Label | Description |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Multiple run values are supported

A single script note can have multiple run label values because each scheduler event independently retrieves matching notes. Stating that the values are mutually exclusive and require separate script copies gives users unnecessary and incorrect configuration guidance.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Fix in Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M This PR changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Confusion regarding some run events (mobileStartup,frontendStartup)

1 participant