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

HTTPS Caused No Dots On Map

Open
#282 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
api, backend

Research direction

Start by tracing the /query endpoint and where its request body is assembled, then compare the generated target IDs with the HTTP IDs used by the data. Done means the query matches the existing target identifiers and returns the expected map results; the issue provides no file or test names to begin with.

Written by the indexing model from the issue text.

Description

bug

The /query is coming back empty. The request body to match on does not have "http" IDs, and so always respond with an empty array (the targets on this data are still http://). See payload below.

{
    "$or": [
        {
            "target": {
                "$in": [
                    "https://devstore.rerum.io/v1/id/62cc789a20274674d431538f",
                    "https://devstore.rerum.io/v1/id/62cc789a20274674d431538f"
                ]
            }
        },
        {
            "target.@id": {
                "$in": [
                    "https://devstore.rerum.io/v1/id/62cc789a20274674d431538f",
                    "https://devstore.rerum.io/v1/id/62cc789a20274674d431538f"
                ]
            }
        },
        {
            "target.id": {
                "$in": [
                    "https://devstore.rerum.io/v1/id/62cc789a20274674d431538f",
                    "https://devstore.rerum.io/v1/id/62cc789a20274674d431538f"
                ]
            }
        }
    ],
    "__rerum.history.next": {
        "$exists": true,
        "$size": 0
    }
}

Not sure if this is behind on something from DEER or if there is hard coded nonsense or what.

Dominant language
HTML
Stars
1
Forks
2
PR merge metrics
No merged PRs in 30d

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 CenterForDigitalHumanities/deer-LR

All issues in CenterForDigitalHumanities/deer-LR

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.