Skip to content
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.

Sign up for GitHub

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

Jump to bottom

#[trigger <expr>] should be rejected but it's treated like #[trigger] #1456

Open
utaal opened this issue Feb 18, 2025 · 0 comments
Open

#[trigger <expr>] should be rejected but it's treated like #[trigger] #1456

utaal opened this issue Feb 18, 2025 · 0 comments

Comments

@utaal
Copy link
Collaborator

utaal commented Feb 18, 2025

The correct syntax for an explicit trigger definition is #![trigger <exprs>]
@utaal utaal changed the title #[trigger <expr>] should be redirected but it's treated like #[trigger] #[trigger <expr>] should be rejected but it's treated like #[trigger] Feb 18, 2025
utaal added a commit that referenced this issue Feb 18, 2025
@utaal
disallow #[trigger <expr>], fixes #1456
ed2381b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@utaal