@angular-wave/angular.ts 0.7.0-beta.0 → 0.7.0-beta.1

package/DEVELOPERS.md

@@ -1,4 +1,4 @@
-# Developing AngularJS
+# Developing AngularTS
 
 - [Development Setup](#setup)
 - [Running Tests](#tests)
@@ -8,12 +8,12 @@
 
 ## <a name="setup"> Development Setup
 
-This document describes how to set up your development environment to build and test AngularJS, and
+This document describes how to set up your development environment to build and test AngularTS, and
 explains the basic mechanics of using `git`, `node`, `yarn` and `grunt`.
 
 ### Installing Dependencies
 
-Before you can build AngularJS, you must install and configure the following dependencies on your
+Before you can build AngularTS, you must install and configure the following dependencies on your
 machine:
 
 - [Git](http://git-scm.com/): The [Github Guide to
@@ -39,34 +39,34 @@ machine:
   but you can also add the grunt command-line tool globally (with `yarn global add grunt-cli`), which allows
   you to leave out the `yarn` prefix for all our grunt commands.
 
-### Forking AngularJS on Github
+### Forking AngularTS on Github
 
-To contribute code to AngularJS, you must have a GitHub account so you can push code to your own
-fork of AngularJS and open Pull Requests in the [GitHub Repository][github].
+To contribute code to AngularTS, you must have a GitHub account so you can push code to your own
+fork of AngularTS and open Pull Requests in the [GitHub Repository][github].
 
 To create a Github account, follow the instructions [here](https://github.com/signup/free).
 Afterwards, go ahead and [fork](http://help.github.com/forking) the
-[main AngularJS repository][github].
+[main AngularTS repository][github].
 
-### Building AngularJS
+### Building AngularTS
 
-To build AngularJS, you clone the source code repository and use Grunt to generate the non-minified
-and minified AngularJS files:
+To build AngularTS, you clone the source code repository and use Grunt to generate the non-minified
+and minified AngularTS files:
 
 ```shell
 # Clone your Github repository:
 git clone https://github.com/<github username>/angular.js.git
 
-# Go to the AngularJS directory:
+# Go to the AngularTS directory:
 cd angular.js
 
-# Add the main AngularJS repository as an upstream remote to your repository:
+# Add the main AngularTS repository as an upstream remote to your repository:
 git remote add upstream "https://github.com/angular/angular.js.git"
 
 # Install JavaScript dependencies:
 yarn install
 
-# Build AngularJS:
+# Build AngularTS:
 yarn grunt package
 ```
 
@@ -79,9 +79,9 @@ directories:
 - `angular-<version>.zip` — The complete zip file, containing all of the release build
   artifacts.
 
-- `angular.js` / `angular.min.js` — The regular and minified core AngularJS script file.
+- `angular.js` / `angular.min.js` — The regular and minified core AngularTS script file.
 
-- `angular-*.js` / `angular-*.min.js` — All other AngularJS module script files.
+- `angular-*.js` / `angular-*.min.js` — All other AngularTS module script files.
 
 - `docs/` — A directory that contains a standalone version of the docs
   (same as served in `docs.angularjs.org`).
@@ -103,7 +103,7 @@ HTTP server. For this purpose, we have made available a local web server based o
    http://localhost:8000/
    ```
 
-   By default, it serves the contents of the AngularJS project directory.
+   By default, it serves the contents of the AngularTS project directory.
 
 3. To access the locally served docs, visit this URL:
    ```text
@@ -170,7 +170,7 @@ yarn grunt --help
 
 ### <a name="e2e-tests"></a> Running the End-to-end Test Suite
 
-AngularJS's end to end tests are run with Protractor. Simply run:
+AngularTS's end to end tests are run with Protractor. Simply run:
 
 ```shell
 yarn grunt test:e2e
@@ -188,7 +188,7 @@ To ensure consistency throughout the source code, keep these rules in mind as yo
   out the existing source code and see the section about [writing documentation](#documentation)
 - With the exceptions listed below, we follow the rules contained in
   [Google's JavaScript Style Guide][js-style-guide]:
-  - **Do not use namespaces**: Instead, wrap the entire AngularJS code base in an anonymous
+  - **Do not use namespaces**: Instead, wrap the entire AngularTS code base in an anonymous
     closure and export our API explicitly rather than implicitly.
   - Wrap all code at **100 characters**.
   - Instead of complex inheritance hierarchies, we **prefer simple objects**. We use prototypal
@@ -197,7 +197,7 @@ To ensure consistency throughout the source code, keep these rules in mind as yo
   - To write concise code that can be better minified, we **use aliases internally** that map to
     the external API. See our existing code to see what we mean.
   - We **don't go crazy with type annotations** for private internal APIs unless it's an internal
-    API that is used throughout AngularJS. The best guidance is to do what makes the most sense.
+    API that is used throughout AngularTS. The best guidance is to do what makes the most sense.
 
 ### Specific topics
 
@@ -228,7 +228,7 @@ The `$compile:badrestrict` error is a good example for a well-defined `minErr`:
 
 We have very precise rules over how our git commit messages can be formatted. This leads to **more
 readable messages** that are easy to follow when looking through the **project history**. But also,
-we use the git commit messages to **generate the AngularJS change log**.
+we use the git commit messages to **generate the AngularTS change log**.
 
 The commit message formatting can be added using a typical git workflow or through the use of a CLI
 wizard ([Commitizen](https://github.com/commitizen/cz-cli)). To use the wizard, run `yarn run commit`
@@ -306,17 +306,17 @@ A detailed explanation can be found in this [document][commit-message-format].
 
 ## <a name="documentation"></a> Writing Documentation
 
-The AngularJS project uses a form of [jsdoc](http://usejsdoc.org/) called ngdoc for all of its code
+The AngularTS project uses a form of [jsdoc](http://usejsdoc.org/) called ngdoc for all of its code
 documentation.
 
 This means that all the docs are stored inline in the source code and so are kept in sync as it
 changes.
 
 There is also extra content (the developer guide, error pages, the tutorial,
-and misceallenous pages) that live inside the AngularJS repository as markdown files.
+and misceallenous pages) that live inside the AngularTS repository as markdown files.
 
 This means that since we generate the documentation from the source code, we can easily provide
-version-specific documentation by simply checking out a version of AngularJS and running the build.
+version-specific documentation by simply checking out a version of AngularTS and running the build.
 
 Extracting the source code documentation, processing and building the docs is handled by the
 documentation generation tool [Dgeni][dgeni].
@@ -368,7 +368,7 @@ is interested in the following block tags:
 - `@example` - specifies an example. This can be a simple code block, or a
   [runnable example](#the-example-tag).
 - `@deprecated` - specifies that the following code is deprecated and should not be used.
-  In The AngularJS docs, there are two specific patterns which can be used to further describe
+  In The AngularTS docs, there are two specific patterns which can be used to further describe
   the deprecation: `sinceVersion="<version>"` and `removeVersion="<version>"`
 
 The `type` in `@param` and `@returns` must be wrapped in `{}` curly braces, e.g. `{Object|Array}`.
@@ -379,7 +379,7 @@ name, e.g. `@param {boolean} [ownPropsOnly=false]`.
 
 Descriptions can contain markdown formatting.
 
-#### AngularJS-specific jsdoc directives
+#### AngularTS-specific jsdoc directives
 
 In addition to the standard jsdoc tags, there are a number that are specific to the Angular
 code-base:
@@ -406,16 +406,16 @@ a directive would have different properties to a filter and so would be document
 commonly used types are:
 
 - `overview` - a general page (guide, api index)
-- `provider` - AngularJS provider, such as `$compileProvider` or `$httpProvider`.
-- `service` - injectable AngularJS service, such as `$compile` or `$http`.
+- `provider` - AngularTS provider, such as `$compileProvider` or `$httpProvider`.
+- `service` - injectable AngularTS service, such as `$compile` or `$http`.
 - `object` - well defined object (often exposed as a service)
 - `function` - function that will be available to other methods (such as a helper function within
   the ng module)
 - `method` - method on an object/service/controller
 - `property` - property on an object/service/controller
-- `event` - AngularJS event that will propagate through the `$scope` tree.
-- `directive` - AngularJS directive
-- `filter` - AngularJS filter
+- `event` - AngularTS event that will propagate through the `$scope` tree.
+- `directive` - AngularTS directive
+- `filter` - AngularTS filter
 - `error` - minErr error description
 
 ### General documentation with Markdown

package/Makefile

@@ -25,7 +25,7 @@ check:
 	./node_modules/.bin/tsc 
 
 types:
-	@rm -rf types
+	@rm -rf @types
 	@echo "Generating *.d.ts"
 	@npx -p typescript tsc --project tsconfig.types.json
 

package/README.md

@@ -3,8 +3,8 @@
 ![Build status](https://github.com/Angular-Wave/angular.ts/actions/workflows/ci.yml/badge.svg)
 [![stats](https://data.jsdelivr.com/v1/package/npm/@angular-wave/angular.ts/badge?style=rounded)](https://www.jsdelivr.com/package/npm/@angular-wave/angular.ts)
 
-This project preserves, modernises and expands the original [AngularJS](https://github.com/angular/angular.js)
-framework. AngularTS is "AngularJS: The Good Parts". It takes the three core pillars of the original – a string-interpolation engine,
+This project preserves, modernises and expands the original [AngularTS](https://github.com/angular/angular.js)
+framework. AngularTS is "AngularTS: The Good Parts". It takes the three core pillars of the original – a string-interpolation engine,
 dependency injection, two-way data-binding – and adds a reactive change-detection model on top of modern build tooling with strong typechecking of TypeScript.
 
 The result is a high-performance, buildless, progressive and battle-tested JS framework that stays as close to Web standards as possible.
@@ -76,10 +76,10 @@ We've set up a separate document for
 
 [![Analytics](https://ga-beacon.appspot.com/UA-8594346-11/angular.js/README.md?pixel)](https://github.com/igrigorik/ga-beacon)
 
-## What to use AngularJS for and when to use it
+## What to use AngularTS for and when to use it
 
-AngularJS is the next generation framework where each component is designed to work with every other
-component in an interconnected way like a well-oiled machine. AngularJS is JavaScript MVC made easy
+AngularTS is the next generation framework where each component is designed to work with every other
+component in an interconnected way like a well-oiled machine. AngularTS is JavaScript MVC made easy
 and done right. (Well it is not really MVC, read on, to understand what this means.)
 
 #### MVC, no, MV\* done the right way!
@@ -89,19 +89,19 @@ Model-View-Controller, is a design pattern, i.e. how the code should be organize
 different parts of an application separated for proper readability and debugging. Model is the data
 and the database. View is the user interface and what the user sees. Controller is the main link
 between Model and View. These are the three pillars of major programming frameworks present on the
-market today. On the other hand AngularJS works on MV\*, short for Model-View-_Whatever_. The
-_Whatever_ is AngularJS's way of telling that you may create any kind of linking between the Model
+market today. On the other hand AngularTS works on MV\*, short for Model-View-_Whatever_. The
+_Whatever_ is AngularTS's way of telling that you may create any kind of linking between the Model
 and the View here.
 
 Unlike other frameworks in any programming language, where MVC, the three separate components, each
-one has to be written and then connected by the programmer, AngularJS helps the programmer by asking
-him/her to just create these and everything else will be taken care of by AngularJS.
+one has to be written and then connected by the programmer, AngularTS helps the programmer by asking
+him/her to just create these and everything else will be taken care of by AngularTS.
 
 #### Interconnection with HTML at the root level
 
-AngularJS uses HTML to define the user's interface. AngularJS also enables the programmer to write
-new HTML tags (AngularJS Directives) and increase the readability and understandability of the HTML
-code. Directives are AngularJS’s way of bringing additional functionality to HTML. Directives
+AngularTS uses HTML to define the user's interface. AngularTS also enables the programmer to write
+new HTML tags (AngularTS Directives) and increase the readability and understandability of the HTML
+code. Directives are AngularTS’s way of bringing additional functionality to HTML. Directives
 achieve this by enabling us to invent our own HTML elements. This also helps in making the code DRY
 (Don't Repeat Yourself), which means once created, a new directive can be used anywhere within the
 application.
@@ -110,32 +110,32 @@ HTML is also used to determine the wiring of the app. Special attributes in the
 to load the app, which components or controllers to use for each element, etc. We specify "what"
 gets loaded, but not "how". This declarative approach greatly simplifies app development in a sort
 of WYSIWYG way. Rather than spending time on how the program flows and orchestrating the various
-moving parts, we simply define what we want and AngularJS will take care of the dependencies.
+moving parts, we simply define what we want and AngularTS will take care of the dependencies.
 
 #### Data Handling made simple
 
-Data and Data Models in AngularJS are plain JavaScript objects and one can add and change properties
+Data and Data Models in AngularTS are plain JavaScript objects and one can add and change properties
 directly on it and loop over objects and arrays at will.
 
 #### Two-way Data Binding
 
-One of AngularJS's strongest features. Two-way Data Binding means that if something changes in the
+One of AngularTS's strongest features. Two-way Data Binding means that if something changes in the
 Model, the change gets reflected in the View instantaneously, and the same happens the other way
 around. This is also referred to as Reactive Programming, i.e. suppose `a = b + c` is being
 programmed and after this, if the value of `b` and/or `c` is changed then the value of `a` will be
-automatically updated to reflect the change. AngularJS uses its "scopes" as a glue between the Model
+automatically updated to reflect the change. AngularTS uses its "scopes" as a glue between the Model
 and View and makes these updates in one available for the other.
 
 #### Less Written Code and Easily Maintainable Code
 
-Everything in AngularJS is created to enable the programmer to end up writing less code that is
+Everything in AngularTS is created to enable the programmer to end up writing less code that is
 easily maintainable and readable by any other new person on the team. Believe it or not, one can
 write a complete working two-way data binded application in less than 10 lines of code. Try and see
 for yourself!
 
 #### Testing Ready
 
-AngularJS has Dependency Injection, i.e. it takes care of providing all the necessary dependencies
-to its controllers and services whenever required. This helps in making the AngularJS code ready for
-unit testing by making use of mock dependencies created and injected. This makes AngularJS more
+AngularTS has Dependency Injection, i.e. it takes care of providing all the necessary dependencies
+to its controllers and services whenever required. This helps in making the AngularTS code ready for
+unit testing by making use of mock dependencies created and injected. This makes AngularTS more
 modular and easily testable thus in turn helping a team create more robust applications.

package/RELEASE.md

@@ -1,4 +1,4 @@
-# AngularJS Release instructions
+# AngularTS Release instructions
 
 ## Compare the list of commits between stable and unstable
 
@@ -38,7 +38,7 @@ scripts/release/release.sh --git-push-dryrun=false --commit-sha=8822a4f --versio
 
 2. The version number and code-name that should be released, not the next version number (e.g. to release 1.2.12 you enter 1.2.12 as release version and the code-name that was picked for 1.2.12, cauliflower-eradication).
 
-3. You will need to have write access to all the AngularJS github dist repositories and publish rights for the AngularJS packages on npm.
+3. You will need to have write access to all the AngularTS github dist repositories and publish rights for the AngularTS packages on npm.
 
 ## Update GitHub milestones
 
@@ -72,7 +72,7 @@ Double check that angularjs.org is up to date with the new release version befor
 use: `git log --format='%aN' v1.2.12..v1.2.13 | sort -u`
 
 2. Write a blog post (for minor releases, not patch releases) and publish it with the "release" tag
-3. Post on twitter as yourself (tweet from your heart; there is no template for this), retweet as @AngularJS
+3. Post on twitter as yourself (tweet from your heart; there is no template for this), retweet as @AngularTS
 
 ## Party!
 

package/SECURITY.md

@@ -2,7 +2,7 @@
 
 ## Supported Versions
 
-**AngularJS support has officially ended as of January 2022.**
+**AngularTS support has officially ended as of January 2022.**
 [See what ending support means](https://docs.angularjs.org/misc/version-support-status)
 and [read the end of life announcement](https://goo.gle/angularjs-end-of-life).
 

package/TRIAGING.md

@@ -1,6 +1,6 @@
 # Triage new issues/PRs on github
 
-This document shows the steps the AngularJS team is using to triage issues.
+This document shows the steps the AngularTS team is using to triage issues.
 The labels are used later on for [planning releases](#assigning-work).
 
 ## Automatic processing
@@ -43,12 +43,12 @@ This process based on the idea of minimizing user pain
 1. Label `frequency: *` – How often does this issue come up? How many developers does this affect? Chose just one of the following:
    - low - obscure issue affecting a handful of developers
    - moderate - impacts a common usage pattern
-   - high - impacts most or all AngularJS apps
+   - high - impacts most or all AngularTS apps
 1. Label `severity: *` - How bad is the issue? Chose just one of the following:
    - security issue
    - regression
    - memory leak
-   - broken expected use - it's hard or impossible for a developer using AngularJS to accomplish something that AngularJS should be able to do
+   - broken expected use - it's hard or impossible for a developer using AngularTS to accomplish something that AngularTS should be able to do
    - confusing - unexpected or inconsistent behavior; hard-to-debug
    - inconvenience - causes ugly/boilerplate code in apps
 1. Label `component: *`