Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):
CLI: 6.4.1
Cross-platform modules: 6.4
Android Runtime: 6.4
iOS Runtime: 6.4
Plugin(s):
Describe the bug
Currently many classes are element locked. This means that the classes work ONLY if you use them with the stock/nativescript-ui plugins. This limits the ability for users to use the new classes on custom plugins (either installed through npm or locally created plugins)
To Reproduce
A simple example: With 1.0 having the following makes both controls styled exactly the same and makes UI consistent:
Environment Provide version numbers for the following components (information can be retrieved by running
tns infoin your project folder or by inspecting thepackage.jsonof the project):Describe the bug Currently many classes are element locked. This means that the classes work ONLY if you use them with the stock/nativescript-ui plugins. This limits the ability for users to use the new classes on custom plugins (either installed through npm or locally created plugins)
To Reproduce A simple example: With 1.0 having the following makes both controls styled exactly the same and makes UI consistent:
With the new 2.0 theme (in non-cmpat mode) having the following styles only the
TextFieldcontrolExpected behavior ALL the classes should have the element locks removed so they can be applied to any custom control.
Sample project
Additional context