openbullet / openbullet/OpenBullet2

[REQUEST]:Result status of Keycheck block enhancement

Open
#1,220 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C#
Stars
2.4k
Forks
602
PR merge metrics
No merged PRs in 30d

Description

This feature request respects the following points:
  • This is a feature request, not a question or a configuration issue; Please visit our forum first to troubleshoot with volunteers, before creating a report. The links can be found here.
  • This issue is not already reported on GitHub (I've searched it).
  • I'm using an up to date version of OpenBullet2. We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
  • I agree to follow OpenBullet's Code of Conduct.
  • This report addresses only a single feature request; If you have multiple feature request, kindly create separate reports for each one.
Description of the feature request

In the Result status of Keycheck block, please add the another condition of result status: Continue; Stop; and Jump to the another block or Jump several blocks; End; ... etc. This feature may expedite the speed and save the status checking.

Is your feature request related to a problem

No response

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Relevant screenshots or videos

No response

Additional information

No response

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.

Research direction

Start by locating the Keycheck block and its Result status handling. Clarify which actions are required for Continue, Stop, Jump, and End, then define the expected control flow and acceptance cases before implementing or testing the feature.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.