hound-search/hound

Hardcoded urls paths

Open

#171 opened on Nov 6, 2015

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (5,470 stars) (606 forks)batch import
enhancementhelp wanted

Description

I was trying to use hound under /hound/ uri on my git server, but I coudn't do it because of the urls in javascript.

All javascript urls are hardcoded like /api/v1/search. This makes usage under a different url path almost impossible.

If possible, it would be good to have relative urls or configurable url namespaces on build.

Contributor guide

Tech stack
javascript
Domain
backenddevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
javascriptweb deploymenturl routing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Review the JavaScript files that contain hardcoded API URLs such as '/api/v1/search'. Explore options to make these URLs relative or configurable via a base path configuration. Check if there is any existing configuration mechanism in the project. Consider how the server handles subpath mounting. Also, look at the existing comment on the issue for any additional clarification.
Hardcoded urls paths · hound-search/hound#171 | Good First Issue