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.
isPersian directive is not working anymore
See original GitHub issue~So everything is working as expected when I do test my DatePicker component in a desktop browser. But isPersian directive has no effect when my testing device is a phone. e.g. Google chrome in Android or Safari in iOS.~
Is this a bug? or am I missing something? please let me know how can I help? Thanks.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
custom directive not working - angular - Stack Overflow
I'm trying to create a directive for redacted/private information. If certain information is not provided a black box should be shown (as if ......
Read more >Introduction to California End of Life Option Act - UCLA Health
This law allows a terminally-ill adult, California resident to request a drug from his or her physician that will end his or her...
Read more >Directive - Angular
Angular only allows directives to apply on CSS selectors that do not cross element boundaries. For the following template HTML, a directive with...
Read more >vue-persian-numbers-directive - npm
A Vue directive that converts Persian char numbers to English char numbers. Latest version: 1.0.2, last published: 5 months ago.
Read more >Nevada Health Response: Coronavirus (COVID-19) in Nevada
An infected person can spread COVID-19 starting 2 days before the person has symptoms (or 2 days before their positive test if they...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @SidMorad, API has changed in v1.1.0 and
isPersianprop has been removed. You can uselocale="fa"instead. here are some examples in the docs.@spostad7 It’s actually right because the style changes applied for
locale="fa"are only because of reversing the direction of some elements, and that’s because Persian is RTL. If in any future release I add another locale for Arabic or any other RTL language, this-rtlclass modifier will be still valid which is not the case with-famodifier.