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

🔧 ub-needs-exchange: the JSON path form of a finding — dotted today, root[...] in ubCode — decide before ubCode vendors

Open
#2,230 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Active
Tech stack
python, rust
Domain
devtools

Research direction

Start with Diagnostic.path in ub-needs-exchange and the sphinx-needs warnings for needs.needimport and needs.external_needs, which print the path as (at <path>). The reference form is render_json_path in rust/ubc_needs/src/json_path.rs, which lives in the ubCode repo. The work is a maintainer decision on the path form, not a code change to make yet. Done means a chosen form, a changelog line on the sphinx-needs side, and a corpus re-vendor plan.

Written by the indexing model from the issue text.

Description

enhancement pkg: ub-needs-exchange

Diagnostic.path in ub-needs-exchange is the reader's dotted form (versions.1.0.needs.A.id), kept in 1.0.0 because the first slice changed no behaviour and sphinx-needs prints (at <path>) in its needs.needimport / needs.external_needs warnings. It is ambiguous for a version name or an id holding a ., and ubCode's house form for a JSON path is root['versions']['1.0'] (rust/ubc_needs/src/json_path.rs, render_json_path).

Choosing one form is a contract change (the corpus compares findings as code + path) AND a sphinx-needs warning-text change, so it needs a changelog line on the sphinx-needs side and a corpus re-vendor on ubCode's. Decide before ubCode vendors the document layer (useblocks/ubcode's vendoring issue references this one).

From the ub-needs-exchange 1.0.0 build (#2219, follow-up F1).

Dominant language
Python
Stars
309
Forks
103
Avg merge
11h 26m
Merged PRs (30d)
118

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 useblocks/sphinx-needs

All issues in useblocks/sphinx-needs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.