Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meta Title Resolution for nested pages #416

Open
3 tasks done
lucie1704 opened this issue Nov 12, 2024 · 0 comments
Open
3 tasks done

Meta Title Resolution for nested pages #416

lucie1704 opened this issue Nov 12, 2024 · 0 comments
Labels
Status: Proposal Request for comments

Comments

@lucie1704
Copy link

lucie1704 commented Nov 12, 2024

Clear and concise description of the problem

Can't find meta title with a nested page like "information/legal-mentions"
I get :
[intlify] Not found '/information/legal-mentions._meta.title' key in 'fr' locale messages.

Suggested solution

Either need to have a way to replicate the nested file architecture on the translation side like

locales/
├── en/
│   ├── home.json
│   ├── about.json
│   └── information/
│       ├── legal-mentions.json
│       └── privacy.json
└── fr/
    ├── home.json
    ├── about.json
    └── information/
        ├── legal-mentions.json
        └── privacy.json

to match the page routing architecture side

pages/
├── home.vue
├── about.vue
└── information/
     ├── legal-mentions.vue
     └── privacy.vue

so that it automatically exports information/legal-mentions keys as information.legal-mentions so that it can automatically target the _meta.title keys in the information/legal-mentions.json

Or else be able to modify the meta title path before resolution to be able to call your said file or even a single file with all meta titles

Alternative

No response

Additional context

I have other ways to update the Page Title like using useHead() with my translation but I want to get read of the intlify warning

Validations

  • Read the Contributing Guidelines.
  • Read the README
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
@lucie1704 lucie1704 added the Status: Proposal Request for comments label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Proposal Request for comments
Projects
None yet
Development

No branches or pull requests

1 participant