i18next / i18next/i18next-node-fs-backend

Crash when saveMissing try to assign to a read only property

Open
#89 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
64
Forks
27
PR merge metrics
No merged PRs in 30d

Description

https://github.com/i18next/i18next/issues/605

Contributor guide

Open the contributing guide

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.

Research direction

Start by reading the linked i18next issue at https://github.com/i18next/i18next/issues/605, then trace the saveMissing handling in this repository. Done means the reported crash when assigning to a read-only property no longer occurs, with the relevant behavior verified by available project checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.