101Loop / 101Loop/HisabKitab-BE
Accepting contact as JSONObject
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
In transactions, when user is adding a transaction, currently system accepts `contact` as `Char`. This should be enhanced to provide a support for accepting this as `JSONObject` rather than `Char`.
For more information refer to iamhssingh/JyessTrading-FE#3
Contributor guide
No contributing guide indexed for this repository
Research direction
Look at the transaction endpoint where contact is currently a Char field. The change likely involves modifying the serializer or model to accept a JSONObject. Check the linked frontend issue iamhssingh/JyessTrading-FE#3 for context on the expected data structure. Test the updated endpoint to ensure it correctly parses and stores the JSON contact data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100