Handle various uses of the path delimiter (/)

Open Beginner friendly
#27 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
api

Research direction

Start by locating the code that builds the Latis request URL and inspect how the base URL and dataset name are joined. Exercise combinations with and without a trailing or leading slash, and consider the issue done when the resulting request contains the path delimiter exactly once at the join.

Written by the indexing model from the issue text.

Description

The base URL is likely to be given as ".../dap2" or ".../dap2/" and the dataset name could start with a "/" (my preference) or not. When building the latis request, we should account for potential duplication of the path delimiter.

Dominant language
Python
Stars
0
Forks
0
No merged PRs in 30d

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 lasp/latis-python-client

All issues in lasp/latis-python-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.