Please add `@rules` multilingual site support feature
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.5k
- Forks
- 468
- Avg merge
- 3h 9m
- Merged PRs (30d)
- 2
Description
What problem does this feature proposal attempt to solve?
To support multilingual sites
As you can see in the image, we use trans to return a specific type of return data to the same language
Which possible solutions should be considered?
Adding the trans feature to @rules solves this problem, for example, translating a translation to rules when it was true
@rules(translation: true) # default false
Contributor guide
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
The issue names the @rules directive and the trans feature but does not mention files or tests. Start by locating the existing @rules implementation and translation handling in the Lighthouse codebase, then define the expected multilingual behavior and how it should be verified for both translated and default rule values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, laravel, php
- Domain
- api, backend, internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100