Encoding URL query parameters with a function

Open
#948 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
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
tooling

Research direction

Start by reading the existing expr functions, especially toJSON, and the Go net/url.Values entry point linked in the issue. Confirm the accepted API and naming with maintainers, then add toQuery for encoded query-string output and verify it against the project's existing function tests.

Written by the indexing model from the issue text.

Description

The functions in expr implement toJSON, and I find myself wanting a toQuery to produce url.Values ^1 (encoded to query string).

My mind is bendy but I think that the expression to compute this with pipes/existing functions is too much for me.

I can create a custom function, is there some need/want for this in expr/, accepting PRs? Is toQuery naming fine if yes, any other expectations to meet for contributions (CLA?)...

Dominant language
Go
Stars
8k
Forks
529
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 expr-lang/expr

All issues in expr-lang/expr

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.