fsprojects / fsprojects/FSharp.AWS.DynamoDB
Empty string support
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 61
- Forks
- 18
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 1
Description
Been running into the empty strings not supported by DynamoDB error from here quite a bit. While it might be an indication of an underlying "issue" with the data, I'm wondering if this might be outdated after coming across this article? Is it worth updating this - and if so, should the aim be to have different types of picklers for key (enforce non-empty strings) and non-key (allow non-empty strings) attributes?
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 with src/FSharp.AWS.DynamoDB/Picklers/PrimitivePicklers.fs at line 40 and compare its empty-string handling with DynamoDB's rules for key and non-key attributes. Trace how these picklers are used, then define and verify whether separate key and non-key behavior is needed; the issue is done when the supported behavior and its scope are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100