openbullet / openbullet/OpenBullet2

[REQUEST]: move the "Requests" block to beginning, followed by functions

Open
#1,225 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

this may sound a silly request but i think it's important, your neighbor (SB) have this block placement that the REQUESTS block is in the beginning, and functions block is below, if we click the requests block then the http block is at the beginning too, as the request block is the most used, as well as the http request is the most used too.

by placing the most used blocks in the beginning we improve apps efficiency, place the functions block right after the requests block as it's the second most used block (i presume)

Image Image
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 UI code that orders the Requests, Functions, and HTTP request blocks, then inspect how the block categories and items are assembled. Reorder the displayed categories so Requests comes first, Functions follows, and the HTTP request block leads within Requests; verify the updated ordering in the application.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
design, desktop
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.