hound-search/hound

Hardcoded urls paths

Open

#171 opened on Nov 6, 2015

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)JavaScript (606 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (5,470 stars)
PR merge metrics
 (No merged PRs in 30d)

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

Research direction
Search for all hardcoded API URL strings in JavaScript files and replace them with a configurable base URL variable, typically set during build or runtime. Then test that the application works under a subpath like /hound/.
Tech stack
javascript
Domain
backendfrontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65