- 🇨🇦Canada SamirMtlHI @jmolivas 
 Thanks for your module it was helpful for my personal project,
 I have figured out a solution to make the module translatable, basically, I implemented 2 new producers in the ContentTypeSchemaExtension that accept the language parameters, so the GraphQl would be :query ($path: String!, $language: String!){ nodeByPathLang(path: $path, language: $language) { ... on NodeArticle { __typename id title path tempKeyWorldMeta summary{ value } author { displayName } body { processed } status created } } }That means big changes in the code, and non-backward compatibilities, maybe I missing something, but I didn't find a way to implement a new ContentTypeLangSchemaExtension class that accepts lang parameters, I have an error "ArticleNode type already declared" 
 It would be helpful if I have some guidance for that,
 I'm on slack, a direct chat will be more effective
- @samirmtl opened merge request.
- Assigned to almunnings
- 🇦🇺Australia almunnings Melbourne, 🇦🇺In 2.x we van now filter content with views. 
 But it would be nice to have language it in the router also.I'll work on this with 2.x. 
- 🇦🇺Australia almunnings Melbourne, 🇦🇺Added langcode filter to route() query, this ticket is considered fixed for 2.x 
- Status changed to Fixedover 2 years ago 11:20am 11 April 2023
- Status changed to Fixedover 2 years ago 10:27pm 11 April 2023