Activate transformer value.to to parse data outgoing to DB
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8.7k
- Forks
- 374
- Avg merge
- 11d 16h
- Merged PRs (30d)
- 1
Description
Hi,
We have a use case in which we would like to protect arbitrary text values writen by our endusers from being registred into the database from reserved characters (notably "new line" \n).
However it seems that feature transform.value.to is forcefully unactivated in the library while transform.value.from can be used.
Unfortunately since user can edit previously registred value we need both transformers to be set in order to maintain consistency.
Could transform.value.to be available in the same way transform.value.from is ?
Thanks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the implementation and tests for transform.value.to and transform.value.from in the Postgres.js codebase. Check how outgoing values are transformed before database writes, then verify that enabling transform.value.to preserves the existing from behavior and handles edited user values consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs, postgresql
- Domain
- database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100