Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Consider supporting `call` for pseudo commands

Open
#454 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend, web-dev

Research direction

No files or tests are named. Start by locating the parser entry point for the existing call ... of form and the handling of on targets. Confirm that call show() on the #modal is accepted and invokes show on the dialog, then add or run the relevant parser and runtime coverage.

Written by the indexing model from the issue text.

Description

Assume there exists a <dialog id="modal" /> on the page.

If I try:

<button _="on click show() the #modal">
Show Modal
</button>

Then this doesn't work, because show is a command, and therefore the () are syntax errors.

I therefore need to instead do:

<button _="on click call show() of #modal">
Show Modal
</button>

In order for it do be correctly interpreted. This is fine, to disambiguate. But what about supporting:

<button _="on click call show() on the #modal">
Show Modal
</button>
Dominant language
JavaScript
Stars
3.8k
Forks
171
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bigskysoftware/_hyperscript

All issues in bigskysoftware/_hyperscript

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.