Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feature: marker fn supports scope

See original GitHub issue

Is there an existing issue for this?

I have searched the existing issues

Is your feature request related to a problem? Please describe

There are situations when I can’t use template translation. Also I need to use translation from one scope in other place. Translation API is good than used in one place. But I need little more flex.

Describe the solution you’d like

marker(key, scope?)

or maybe marker("scope.key") like in comment marker /** t(scope.key) */ when used in scoped component/module

Describe alternatives you’ve considered

No response

Describe alternatives you’ve considered

Additional context

No response

I would like to make a pull request for this feature

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:10 (3 by maintainers)

Top GitHub Comments

2reactions

FloNeucommented, Aug 3, 2022

I was looking for this too… i am pretty sure he means he would like a way to use the marker function to scope the translation key and extract it into the scope-file (like marker( test1, admin ) -> creates the key in the admin-scope file)… right now when I use the marker function I can only put the keys in the top-level translation file, right? (at least I haven’t found a way to do it otherwise)

1reaction

shaharkazazcommented, Dec 16, 2022

@christophbuehler Thanks for sharing! Anyways the signature needs to be fixed, but I think that API wise it’s preferred to just support marker('scope.a') to be consistent with the comment extraction API. What do you think?

Top Results From Across the Web

Issues · ngneat/transloco-keys-manager - GitHub

Issues list ; Bug: transloco-keys-manager does not extract text from the attribute directive · #145 opened on Oct 30 ; Feature: Add support...

auto_enums - Rust - Docs.rs

Positions where #[auto_enum] can be used. · Supported syntax · Parse nested branches · Expression that no value will be returned · Expression...

Documentation - a JavaScript library for interactive maps

Runs the given function fn when the map gets initialized with a view (center and zoom) and at least one layer, or immediately...

User Manual - rust-analyzer

You'll need Cargo, nodejs (matching a supported version of VS Code) and npm for this. ... fn main() { pda$0 } # pub...

Lingo4G, clustering engine reference

Lingo4G supports automatic feature discovery resulting in labels based on sequences of ... Each document in scope is represented by one point (marker)....