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

Access params in operations using accessors instead of the 'params' object.

Open
#421 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
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, react, ruby
Domain
full-stack

Research direction

Start by tracing Hyperstack operations and the existing component behavior for param_accessor_style :accessors. Done means operation parameters can be accessed through same-name accessors while retaining the existing params object convention and keeping component accessors working; identify or add focused coverage for both paths.

Written by the indexing model from the issue text.

Description

Setting param_accessor_style :accessors for Hyperstack components enables accessing component parameters directly
without the need to prepend the 'params' object.
This isn't supported for operations and it would be a great syntactic sugar, if you could also access operations' parameters using an accessor of the same name.
This call convention will also align the use of params across components and operations.

Dominant language
JavaScript
Stars
538
Forks
41
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 hyperstack-org/hyperstack

All issues in hyperstack-org/hyperstack

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.