validate QSettings APIs

Open
#1,585 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp, python
Domain
api, desktop

Research direction

Start by locating the QSettings API handling for clean-install folders and compare how the Python API and C API treat spaces in names. Verify the behavior on a clean install and define one canonical folder name; done means both APIs create or reference only that single name.

Written by the indexing model from the issue text.

Description

Component: UI Effort: Low Impact: Low

We've had a number of QSettings folders made with "Vector 35" and some made with Vector35 in previous versions.

At some point we need to verify that going forward clean installs only create one, or the other (though it's at least partially exacerbated by the fact that the Python API and the C API handle spaces in names differently afaict.)

Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

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 Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.