Add support for parsing SRV records to nsl()

Open
#16 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
r
Domain
networking

Research direction

Start by locating the nsl() entry point and tracing how it currently queries and parses name-service results. Investigate the SRV record shape and the package's existing tests or platform-specific lookup code; done means nsl() can return parsed SRV records for the stated micro-services use case.

Written by the indexing model from the issue text.

Description

feature help wanted :heart:

Could support for parsing SRV records be added to nsl()?

I've been looking for a self-contained way to query SRV records, ultimately to enable shiny apps to find plumber API endpoints in a micro-services environment. pingr::nsl() is allllmost there. 😄

Dominant language
C
Stars
38
Forks
9
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 r-lib/pingr

All issues in r-lib/pingr

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.