Add parsers for the background css shorthand property, make ViewBase unit testable in node environment
Add background parser and linear-gradient parser
Use sticky regexes
Simplify some types, introduce generic Parsed<T> instead of & TokenRange
Apply each parser to return a { start, end, value } object
Move the css selector parser to the css/parser and unify types
Add the first steps toward building homegrown css parser
Add somewhat standards compliant tokenizer, add baseline, rework and shady css parsers
Enable all tests again, skip flaky perf test
Improve css parser tokenizer by converting some char token types to simple string
Implement 'parse a stylesheet'
Add gonzales css-parser
Add parseLib and css-tree perf
Add a thin parser layer that will convert CSS3 tokens to values, for now output is compatible with rework
Make root tsc green
Return the requires of tns-core-modules to use relative paths for webpack to work
Implement support for '@import 'url-string';
Fix function parser, function-token is no-longer neglected
Make the style-scope be able to load from "css" and "css-ast" modules
Add a loadAppCss event so theme can be added to snapshot separately from loaded
- Use path mappings in tsconfig.json to resolve module typings
- Only use ambient mobules for global API's
- Move single-file modules to a subdir with the same name so that
we can provide a hand-written typing next to it (via package.json)
- Delete all mentions of tns-core-modules.d.ts
- Delete reference d.ts assembly build steps. Not needed anymore.
- HACK! Use a <reference> for global typings in application.d.ts
to avoid publishing a separate @types/tns-core-modules package.
- Rename declarations.d.ts to tns-core-modules.d.ts to preserve
JS project mappings in references.d.ts (the only place we use those)
Fixes name clashes and uses Node-compatible typings where possible.
Changes:
- setTimout et al now return NodeJS.Timer instead of number
- No "console" module anymore. Everyone uses it through global.console
anyway.
- We have a typed "global" instance with exposed properties now. Any
"freeform" accesses must go through a `(<any>global).blah` cast.
- remove tns-core-modules.{base,es6,es2015}.d.ts. Those were needed
as workarounds for the ES6/DOM/Node type clashes.
Less than 30 erros left, let's hope it still works
Added lib.*.d.ts from typescript, removed lib and dom stuff, added by hand XHR, alert etc. .d.ts-es for polyfills
Roll back some changes involved in separating UIEvent for dom and ios
Test combined dts-es will now use lib, while internally we will not to avoid UIEvent conflict with dom stuff
Don't use a filepath ending in .js, let the require implementation
resolve the js file. This makes it easier to require the correct
platform-specific file when bundling by switching the webpack
`resolve.extensions` setting.
Add android definitions to check if they will get downloaded
Set the language to android
Attempt starting the app
Add a new redirection to the testapp-runner - a runOnly verb
Disable the install prompt
Enable the buildOnly- and runOnly- commands
Fix the version of the packages
Comment cleanup code. Workflow to be reworked
Install android 23 to make the app build
Build the test app with the @next android runtime
Add @next ability. Build with it
Specify oracle java version 8
Use switcher to switch to oraclejdk8
Switch to a single step so that build breaks on first failure
Reorder attempting to use higher nodejs
Attempt using node 5.10.1
Detect test failure
Add detection for test failures
Decrease verbosity
Extract the test checkers to a separate script
Unignore the build folder recursively. Add the fixed script
Remove the redundant node-version messages
Run the tests with Api level 21
The grunt file respected the --leavecomments option, used when
generating the How-To articles of the API Reference. This was broken with
the passthrough option to grunt-ts.
- tns-core-modules-base.d.ts containing modules definitions with as little
platform stuff as possible. Angular apps will reference this one.
- tns-core-modules.es6.d.ts adding some platform stuff to base. Intended to
be used in environments supporting ES6 (obviously)
- tns-core-modules.d.ts adding to the previous one definitions for our ES6
polyfills: promises, collections, weakmaps, etc. The usual reference point
for most apps.
