What is the current behavior?

Currently while using import { Enums } from '@nativescript/core'; in es2017 there was no clear way to delineate between type definition and namespace/module as they were overloaded throughout.

import { Enums } from '@nativescript/core';

const left = Enums.TextAlignment.left; // works
const leftAssignment: Enums.TextAlignment = 'left'; // doesn't work

There was a workaround that you could do:

const left: typeof Enums.TextAlignment;

...but that's pretty inconvenient.

Also the barrel was missing a few ui property getter/setters for plugin usage.

What is the new behavior?

Type has been added to suffix any exported type named symbols for better clarity and usage while allowing the namespace/module to work as normal as well.

import { Enums } from '@nativescript/core';

const left = Enums.TextAlignment.left; // works
const leftAssignment: Enums.TextAlignmentType = 'left'; // works

This also adds the additional getter/setters for plugin usage:

import { 
  letterSpacingProperty, 
  textAlignmentProperty, 
  textDecorationProperty, 
  textTransformProperty, 
  whiteSpaceProperty, 
  lineHeightProperty 
} from '@nativescript/core';

/cc @PeterStaev