New Rosetta features
Open
Nobody has claimed this yet.
type:epic
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
This is an issue for collecting other issues/features we might want in future versions of Rosetta.
Difficulty
- easy = 1
- medium = 2
- hard = 3
Value
- unimportant = 1
- nice-to-have = 2
- important = 3
| Issue | Actionable for LM? | Value | Difficulty | Done? | Notes |
|---|---|---|---|---|---|
| Integrate website styling? | No | 2 | 2 | ❌ | Requires coordination with MP. Website uses Less. Rosetta would have to use classes that the website uses. |
| Integrate website header? | No | 2 | 3 | ❌ | Requires work from MP. Right now, the header is written in TomCat. Things are ported to React on an as-needed basis. Let's do this after we migrate the website header to React. (This is probably a year away because there's a lot of pages that depend on the header we'd also need to port.) |
| https://github.com/phetsims/rosetta/issues/301 | No | 3 | 2 | ❌ | Requires MP to add translator's locale(s) to check-login object. |
| https://github.com/phetsims/rosetta/issues/354 | Yes | 2 | 2 | ✅ | n/a |
| https://github.com/phetsims/rosetta/issues/336 | Yes | 2 | 1 | ✅ | n/a |
| https://github.com/phetsims/rosetta/issues/333 | No | 2 | 2 | ❌ | This is two issues: (1) Should we match the English string? (2) Should we ensure the opening tags have corresponding closing tags? It would be nice to get translator feedback on (1). |
| https://github.com/phetsims/rosetta/issues/337 | Yes | 2 | 2 | ❌ | n/a |
| https://github.com/phetsims/rosetta/issues/349 | No | 2 | 1 | ✅ | We should discuss this in a design meeting so that Rosetta isn't adding band-aid solutions to problems that were introduced in upstream design decisions. |
| https://github.com/phetsims/rosetta/issues/353 | No | ? | ? | ❌ | n/a |
| https://github.com/phetsims/rosetta/issues/356 | Yes | 2 | 1 | ✅ | Related to https://github.com/phetsims/rosetta/issues/349. |
| https://github.com/phetsims/rosetta/issues/327 | No | 2 | 3 | ❌ | Requires design from LM and JB. |
| https://github.com/phetsims/rosetta/issues/325 | No | 2 | ? | ❌ | Wait until usePrompt and useBlocker are stable in React Router V6. (They are added, but unstable as of January 21st, 2023.) |
| https://github.com/phetsims/rosetta/issues/323 | Yes | 2 | 1 | ❌ | Have JB review this. |
| https://github.com/phetsims/rosetta/issues/316 | No | 1 | ? | ❌ | Need to figure out how to get repo's SHA in order to bust GitHub's cache. |
| https://github.com/phetsims/rosetta/issues/314 | No | 3 | ? | ❌ | Requires design time. |
| https://github.com/phetsims/rosetta/issues/311 | No | 3 | 2 | ❌ | LM needs to know what TS rules we want to include for Rosetta. |
| https://github.com/phetsims/rosetta/issues/304 | No | 2 | 2 | ❌ | Need to figure out how to tell when a file was pushed to GitHub. |
| https://github.com/phetsims/rosetta/issues/302 | No | 3 | ? | ❌ | Don't even have a rough idea of how to do this. |
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
No files, tests, or entry points are named. Start by reviewing the linked issues and the table's dependency notes, especially the items requiring design or coordination with MP, LM, or JB; this issue is complete only when a specific future feature has been selected and given actionable scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100