@angular-wave/angular.ts 0.0.7 → 0.0.8

package/docs/hugo.yaml

@@ -0,0 +1,220 @@
+baseURL: https://example.docsy.dev
+title: Goldydocs
+
+# cSpell:ignore goldmark github hugo readingtime docsy subdir lastmod pygments linenos catmullrom norsk gu
+
+# Language settings
+contentDir: content/en
+defaultContentLanguage: en
+defaultContentLanguageInSubdir: false
+# Useful when translating.
+enableMissingTranslationPlaceholders: true
+
+enableRobotsTXT: true
+
+# Will give values to .Lastmod etc.
+enableGitInfo: true
+
+# Comment out to enable taxonomies in Docsy
+# disableKinds: [taxonomy, taxonomyTerm]
+
+# You can add your own taxonomies
+taxonomies:
+  tag: tags
+  category: categories
+
+# Highlighting config
+pygmentsCodeFences: true
+pygmentsUseClasses: false
+# Use the new Chroma Go highlighter in Hugo.
+pygmentsUseClassic: false
+# pygmentsOptions: "linenos=table"
+# See https://help.farbox.com/pygments.html
+pygmentsStyle: tango
+
+# Configure how URLs look like per section.
+permalinks:
+  blog: /:section/:year/:month/:day/:slug/
+
+# Image processing configuration.
+imaging:
+  resampleFilter: CatmullRom
+  quality: 75
+  anchor: smart
+
+# Language configuration
+languages:
+  en:
+    languageName: English
+    title: Goldydocs
+    params:
+      description: A Docsy example site
+  # cSpell:disable
+  'no':
+    languageName: Norsk
+    contentDir: content/no
+    title: Gulldoks
+    params:
+      description: Docsy er operativsystem for skyen
+      time_format_default: 02.01.2006
+      time_format_blog: 02.01.2006
+  fa:
+    languageDirection: rtl
+    languageName: "فارسی (Persian)"
+    contentDir: content/fa
+    title: "اسناد گلدی"
+    params:
+      description: "یک نمونه برای پوسته داکسی"
+      time_format_default: 2006.01.02
+      time_format_blog: 2006.01.02
+  # cSpell:enable
+
+markup:
+  goldmark:
+    parser:
+      attribute:
+        block: true
+    renderer:
+      unsafe: true
+  highlight:
+    # See a complete list of available styles at https://xyproto.github.io/splash/docs/all.html
+    style: tango
+    # Uncomment if you want your chosen highlight style used for code blocks without a specified language
+    # guessSyntax: true
+
+# Everything below this are Site Params
+
+# Comment out if you don't want the "print entire section" link enabled.
+outputs:
+  section: [HTML, print, RSS]
+
+params:
+  taxonomy:
+    # set taxonomyCloud = [] to hide taxonomy clouds
+    taxonomyCloud: [tags, categories]
+
+    # If used, must have same length as taxonomyCloud
+    taxonomyCloudTitle: [Tag Cloud, Categories]
+
+    # set taxonomyPageHeader = [] to hide taxonomies on the page headers
+    taxonomyPageHeader: [tags, categories]
+
+  privacy_policy: https://policies.google.com/privacy
+
+  # First one is picked as the Twitter card image if not set on page.
+  # images: [images/project-illustration.png]
+
+  # Menu title if your navbar has a versions selector to access old versions of your site.
+  # This menu appears only if you have at least one [params.versions] set.
+  version_menu: Releases
+
+  # Flag used in the "version-banner" partial to decide whether to display a
+  # banner on every page indicating that this is an archived version of the docs.
+  # Set this flag to "true" if you want to display the banner.
+  archived_version: false
+
+  # The version number for the version of the docs represented in this doc set.
+  # Used in the "version-banner" partial to display a version number for the
+  # current doc set.
+  version: 0.0
+
+  # A link to latest version of the docs. Used in the "version-banner" partial to
+  # point people to the main doc site.
+  url_latest_version: https://example.com
+
+  # Repository configuration (URLs for in-page links to opening issues and suggesting changes)
+  github_repo: https://github.com/google/docsy-example
+
+  # An optional link to a related project repo. For example, the sibling repository where your product code lives.
+  github_project_repo: https://github.com/google/docsy
+
+  # Specify a value here if your content directory is not in your repo's root directory
+  # github_subdir: ""
+
+  # Uncomment this if your GitHub repo does not have "main" as the default branch,
+  # or specify a new value if you want to reference another branch in your GitHub links
+  github_branch: main
+
+  # Google Custom Search Engine ID. Remove or comment out to disable search.
+  gcs_engine_id: d72aa9b2712488cc3
+
+  # Enable Lunr.js offline search
+  offlineSearch: false
+
+  # Enable syntax highlighting and copy buttons on code blocks with Prism
+  prism_syntax_highlighting: false
+
+  copyright:
+    authors: Docsy Authors | [CC BY 4.0](https://creativecommons.org/licenses/by/4.0) |
+    from_year: 2018
+
+  # User interface configuration
+  ui:
+    # Set to true to disable breadcrumb navigation.
+    breadcrumb_disable: false
+    # Set to false if you don't want to display a logo (/assets/icons/logo.svg) in the top navbar
+    navbar_logo: true
+    # Set to true if you don't want the top navbar to be translucent when over a `block/cover`, like on the homepage.
+    navbar_translucent_over_cover_disable: false
+    # Enable to show the side bar menu in its compact state.
+    sidebar_menu_compact: false
+    # Set to true to hide the sidebar search box (the top nav search box will still be displayed if search is enabled)
+    sidebar_search_disable: false
+
+    # Adds a H2 section titled "Feedback" to the bottom of each doc. The responses are sent to Google Analytics as events.
+    # This feature depends on [services.googleAnalytics] and will be disabled if "services.googleAnalytics.id" is not set.
+    # If you want this feature, but occasionally need to remove the "Feedback" section from a single page,
+    # add "hide_feedback: true" to the page's front matter.
+    feedback:
+      enable: true
+      # The responses that the user sees after clicking "yes" (the page was helpful) or "no" (the page was not helpful).
+      'yes': >-
+        Glad to hear it! Please <a href="https://github.com/USERNAME/REPOSITORY/issues/new">tell us how we can improve</a>.
+      'no': >-
+        Sorry to hear that. Please <a href="https://github.com/USERNAME/REPOSITORY/issues/new">tell us how we can improve</a>.
+
+    # Adds a reading time to the top of each doc.
+    # If you want this feature, but occasionally need to remove the Reading time from a single page,
+    # add "hide_readingtime: true" to the page's front matter
+    readingtime:
+      enable: false
+
+  links:
+    # End user relevant links. These will show up on left side of footer and in the community page if you have one.
+    user:
+      - name: User mailing list
+        url: https://example.org/mail
+        icon: fa fa-envelope
+        desc: Discussion and help from your fellow users
+      - name: Twitter
+        url: https://example.org/twitter
+        icon: fab fa-twitter
+        desc: Follow us on Twitter to get the latest news!
+      - name: Stack Overflow
+        url: https://example.org/stack
+        icon: fab fa-stack-overflow
+        desc: Practical questions and curated answers
+    # Developer relevant links. These will show up on right side of footer and in the community page if you have one.
+    developer:
+      - name: GitHub
+        url: https://github.com/google/docsy
+        icon: fab fa-github
+        desc: Development takes place here!
+      - name: Slack
+        url: https://example.org/slack
+        icon: fab fa-slack
+        desc: Chat with other project developers
+      - name: Developer mailing list
+        url: https://example.org/mail
+        icon: fa fa-envelope
+        desc: Discuss development issues around the project
+
+module:
+  # Uncomment the next line to build and serve using local docsy clone declared in the named Hugo workspace:
+  # workspace: docsy.work
+  hugoVersion:
+    extended: true
+    min: 0.110.0
+  imports:
+    - path: github.com/google/docsy
+      disable: false

package/docs/layouts/404.html

@@ -0,0 +1,7 @@
+{{ define "main" -}}
+<div class="td-content">
+  <h1>Not found</h1>
+  <p>Oops! This page doesn't exist. Try going back to the <a href="{{ "" | relURL }}">home page</a>.</p>
+  <p>You can learn how to make a 404 page like this in <a href="https://gohugo.io/templates/404/">Custom 404 Pages</a>.</p>
+</div>
+{{- end }}

package/docs/layouts/_default/_markup/render-heading.html

@@ -0,0 +1 @@
+{{ template "_default/_markup/td-render-heading.html" . }}

package/docs/netlify.toml

@@ -0,0 +1,12 @@
+# Hugo build configuration for Netlify
+# (https://gohugo.io/hosting-and-deployment/hosting-on-netlify/#configure-hugo-version-in-netlify)
+
+[build]
+command = "npm run build:preview"
+publish = "public"
+
+[build.environment]
+GO_VERSION = "1.22.2"
+
+[context.production]
+command = "npm run build:production"

package/docs/package.json

@@ -0,0 +1,42 @@
+{
+  "name": "docsy-example-site",
+  "version": "0.10.0",
+  "version.next": "0.10.1-dev.0-unreleased",
+  "description": "Example site that uses Docsy theme for technical documentation.",
+  "repository": "github:google/docsy-example",
+  "homepage": "https://example.docsy.dev",
+  "author": "Docsy Authors",
+  "license": "Apache-2.0",
+  "bugs": "https://github.com/google/docsy-example/issues",
+  "spelling": "cSpell:ignore HTMLTEST precheck postbuild -",
+  "scripts": {
+    "_build": "npm run _hugo-dev --",
+    "_check:links": "echo IMPLEMENTATION PENDING for check-links; echo",
+    "_hugo": "hugo --cleanDestinationDir",
+    "_hugo-dev": "npm run _hugo -- -e dev -DFE",
+    "_local": "npx cross-env HUGO_MODULE_WORKSPACE=docsy.work",
+    "_serve": "npm run _hugo-dev -- --minify serve --renderToMemory",
+    "build:preview": "npm run _hugo-dev -- --minify --baseURL \"${DEPLOY_PRIME_URL:-/}\"",
+    "build:production": "npm run _hugo -- --minify",
+    "build": "npm run _build -- ",
+    "check:links:all": "HTMLTEST_ARGS= npm run _check:links",
+    "check:links": "npm run _check:links",
+    "clean": "rm -Rf public/* resources",
+    "local": "npm run _local -- npm run",
+    "make:public": "git init -b main public",
+    "precheck:links:all": "npm run build",
+    "precheck:links": "npm run build",
+    "postbuild:preview": "npm run _check:links",
+    "postbuild:production": "npm run _check:links",
+    "serve": "npm run _serve",
+    "test": "npm run check:links",
+    "update:dep": "npm install --save-dev autoprefixer@latest postcss-cli@latest",
+    "update:hugo": "npm install --save-dev --save-exact hugo-extended@latest"
+  },
+  "devDependencies": {
+    "autoprefixer": "^10.4.14",
+    "cross-env": "^7.0.3",
+    "hugo-extended": "0.126.1",
+    "postcss-cli": "^11.0.0"
+  }
+}

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@angular-wave/angular.ts",
   "license": "MIT",
-  "version": "0.0.7",
+  "version": "0.0.8",
   "type": "module",
   "main": "dist/angular-ts.cjs.js",
   "module": "dist/angular-ts.esm.js",

package/src/core/compile.js

@@ -49,13 +49,11 @@ let config = { TTL: 10 };
  *
  * @description
  */
-// eslint-disable-next-line no-use-before-define
 $CompileProvider.$inject = ["$provide", "$$sanitizeUriProvider"];
 
 export function $CompileProvider($provide, $$sanitizeUriProvider) {
   const hasDirectives = {};
   const Suffix = "Directive";
-  const COMMENT_DIRECTIVE_REGEXP = /^\s*directive:\s*([\w-]+)\s+(.*)$/;
   const CLASS_DIRECTIVE_REGEXP = /(([\w-]+)(?::([^;]+))?;?)/;
   const ALL_OR_NOTHING_ATTRS = {
     ngSrc: true,
@@ -558,62 +556,6 @@ export function $CompileProvider($provide, $$sanitizeUriProvider) {
     return config.TTL;
   };
 
-  let commentDirectivesEnabledConfig = true;
-  /**
-   * @ngdoc method
-   * @name $compileProvider#commentDirectivesEnabled
-   * @description
-   *
-   * It indicates to the compiler
-   * whether or not directives on comments should be compiled.
-   * Defaults to `true`.
-   *
-   * Calling this function with false disables the compilation of directives
-   * on comments for the whole application.
-   * This results in a compilation performance gain,
-   * as the compiler doesn't have to check comments when looking for directives.
-   * This should however only be used if you are sure that no comment directives are used in
-   * the application (including any 3rd party directives).
-   *
-   * @param {boolean} enabled `false` if the compiler may ignore directives on comments
-   * @returns {boolean|object} the current value (or `this` if called as a setter for chaining)
-   */
-  this.commentDirectivesEnabled = function (value) {
-    if (arguments.length) {
-      commentDirectivesEnabledConfig = value;
-      return this;
-    }
-    return commentDirectivesEnabledConfig;
-  };
-
-  let cssClassDirectivesEnabledConfig = true;
-  /**
-   * @ngdoc method
-   * @name $compileProvider#cssClassDirectivesEnabled
-   * @description
-   *
-   * It indicates to the compiler
-   * whether or not directives on element classes should be compiled.
-   * Defaults to `true`.
-   *
-   * Calling this function with false disables the compilation of directives
-   * on element classes for the whole application.
-   * This results in a compilation performance gain,
-   * as the compiler doesn't have to check element classes when looking for directives.
-   * This should however only be used if you are sure that no class directives are used in
-   * the application (including any 3rd party directives).
-   *
-   * @param {boolean} enabled `false` if the compiler may ignore directives on element classes
-   * @returns {boolean|object} the current value (or `this` if called as a setter for chaining)
-   */
-  this.cssClassDirectivesEnabled = function (value) {
-    if (arguments.length) {
-      cssClassDirectivesEnabledConfig = value;
-      return this;
-    }
-    return cssClassDirectivesEnabledConfig;
-  };
-
   /**
    * The security context of DOM Properties.
    * @private
@@ -737,9 +679,6 @@ export function $CompileProvider($provide, $$sanitizeUriProvider) {
       const SIMPLE_ATTR_NAME = /^\w/;
       const specialAttrHolder = window.document.createElement("div");
 
-      const commentDirectivesEnabled = commentDirectivesEnabledConfig;
-      const cssClassDirectivesEnabled = cssClassDirectivesEnabledConfig;
-
       // The onChanges hooks should all be run together in a single digest
       // When changes occur, the call to trigger their hooks will be added to this queue
       let onChangesQueue;
@@ -1574,44 +1513,11 @@ export function $CompileProvider($provide, $$sanitizeUriProvider) {
               node.setAttribute("autocomplete", "off");
             }
 
-            // use class as directive
-            if (!cssClassDirectivesEnabled) break;
-            // TODO: migrate to classList
-            className = node.className;
-            if (isObject(className)) {
-              // Maybe SVGAnimatedString
-              className = className.animVal;
-            }
-            if (isString(className) && className !== "") {
-              while ((match = CLASS_DIRECTIVE_REGEXP.exec(className))) {
-                nName = directiveNormalize(match[2]);
-                if (
-                  addDirective(
-                    directives,
-                    nName,
-                    "C",
-                    maxPriority,
-                    ignoreDirective,
-                  )
-                ) {
-                  attrs[nName] = trim(match[3]);
-                }
-                className = className.substr(match.index + match[0].length);
-              }
-            }
             break;
           case Node.TEXT_NODE:
             addTextInterpolateDirective(directives, node.nodeValue);
             break;
-          case Node.COMMENT_NODE:
-            if (!commentDirectivesEnabled) break;
-            collectCommentDirectives(
-              node,
-              directives,
-              attrs,
-              maxPriority,
-              ignoreDirective,
-            );
+          default:
             break;
         }
 
@@ -1619,32 +1525,6 @@ export function $CompileProvider($provide, $$sanitizeUriProvider) {
         return directives;
       }
 
-      function collectCommentDirectives(
-        node,
-        directives,
-        attrs,
-        maxPriority,
-        ignoreDirective,
-      ) {
-        // function created because of performance, try/catch disables
-        // the optimization of the whole function #14848
-        try {
-          const match = COMMENT_DIRECTIVE_REGEXP.exec(node.nodeValue);
-          if (match) {
-            const nName = directiveNormalize(match[1]);
-            if (
-              addDirective(directives, nName, "M", maxPriority, ignoreDirective)
-            ) {
-              attrs[nName] = trim(match[2]);
-            }
-          }
-        } catch (e) {
-          // turns out that under some circumstances IE9 throws errors when one attempts to read
-          // comment's node value.
-          // Just ignore it and continue. (Can't seem to reproduce in test case.)
-        }
-      }
-
       /**
        * Given a node with a directive-start it collects all of the siblings until it finds
        * directive-end.
@@ -3548,51 +3428,19 @@ export function $CompileProvider($provide, $$sanitizeUriProvider) {
   ];
 }
 
-function SimpleChange(previous, current) {
-  this.previousValue = previous;
-  this.currentValue = current;
-}
-SimpleChange.prototype.isFirstChange = function () {
-  return this.previousValue === _UNINITIALIZED_VALUE;
-};
-
-/**
- * @ngdoc type
- * @name $compile.directive.Attributes
- *
- * @description
- * A shared object between directive compile / linking functions which contains normalized DOM
- * element attributes. The values reflect current binding state `{{ }}`. The normalization is
- * needed since all of these are treated as equivalent in AngularJS:
- *
- * ```
- *    <span ng:bind="a" ng-bind="a" data-ng-bind="a" x-ng-bind="a">
- * ```
- */
-
-/**
- * @ngdoc property
- * @name $compile.directive.Attributes#$attr
- *
- * @description
- * A map of DOM element attribute names to the normalized name. This is
- * needed to do reverse lookup from normalized name back to actual name.
- */
+class SimpleChange {
+  constructor(previous, current) {
+    this.previousValue = previous;
+    this.currentValue = current;
+  }
 
-/**
- * @ngdoc method
- * @name $compile.directive.Attributes#$set
- * @kind function
- *
- * @description
- * Set DOM element attribute value.
- *
- *
- * @param {string} name Normalized element attribute name of the property to modify. The name is
- *          reverse-translated using the {@link ng.$compile.directive.Attributes#$attr $attr}
- *          property to the original name.
- * @param {string} value Value to set the attribute to. The value can be an interpolated string.
- */
+  /**
+   * @returns {boolean}
+   */
+  isFirstChange() {
+    return this.previousValue === _UNINITIALIZED_VALUE;
+  }
+}
 
 function tokenDifference(str1, str2) {
   let values = "";

package/src/core/compile.md

@@ -121,7 +121,7 @@
 -
 - ### Life-cycle hooks
 - Directive controllers can provide the following methods that are called by AngularJS at points in the life-cycle of the
-- directive:
+- directive.The following hooks can be defined on the controller prototype or added to the controller inside its constructor:
 - - `$onInit()` - Called on each controller after all the controllers on an element have been constructed and
 - had their bindings initialized (and before the pre & post linking functions for the directives on
 - this element). This is a good place to put initialization code for your controller.
@@ -136,6 +136,8 @@
 - could be useful if you wish to perform a deep equality check, or to check a Date object, changes to which would not
 - be detected by AngularJS's change detector and thus not trigger `$onChanges`. This hook is invoked with no arguments;
 - if detecting changes, you must store the previous value(s) for comparison to the current values.
+- Changes to the model inside `$doCheck` will trigger new turns of the digest loop, which will cause the changes to be
+- propagated throughout the application.
 - - `$onDestroy()` - Called on a controller when its containing scope is destroyed. Use this hook for releasing
 - external resources, watches and event handlers. Note that components have their `$onDestroy()` hooks called in
 - the same order as the `$scope.$broadcast` events are triggered, which is top down. This means that parent
@@ -145,21 +147,7 @@
 - Note that child elements that contain `templateUrl` directives will not have been compiled and linked since
 - they are waiting for their template to load asynchronously and their own compilation and linking has been
 - suspended until that occurs.
--
-- #### Comparison with life-cycle hooks in the new Angular
-- The new Angular also uses life-cycle hooks for its components. While the AngularJS life-cycle hooks are similar there are
-- some differences that you should be aware of, especially when it comes to moving your code from AngularJS to Angular:
--
-- - AngularJS hooks are prefixed with `$`, such as `$onInit`. Angular hooks are prefixed with `ng`, such as `ngOnInit`.
-- - AngularJS hooks can be defined on the controller prototype or added to the controller inside its constructor.
-- In Angular you can only define hooks on the prototype of the Component class.
-- - Due to the differences in change-detection, you may get many more calls to `$doCheck` in AngularJS than you would to
-- `ngDoCheck` in Angular.
-- - Changes to the model inside `$doCheck` will trigger new turns of the digest loop, which will cause the changes to be
-- propagated throughout the application.
-- Angular does not allow the `ngDoCheck` hook to trigger a change outside of the component. It will either throw an
-- error or do nothing depending upon the state of `enableProdMode()`.
--
+
 - #### Life-cycle hook examples
 -
 - This example shows how you can check for mutations to a Date object even though the identity of the object
@@ -1016,6 +1004,7 @@
 - Result: <span ng-class="{'something': something} {'else': else}" ng-show="!condition otherCondition"></span>
 - ```
 
+  ``
   ```
 
 -
@@ -1190,3 +1179,49 @@
 - `myEvent` must be written as `ng-on-my_event="expression"`.
 -
 - \*/
+
+/\*\*
+
+- @ngdoc type
+- @name $compile.directive.Attributes
+-
+- @description
+- A shared object between directive compile / linking functions which contains normalized DOM
+- element attributes. The values reflect current binding state `{{ }}`. The normalization is
+- needed since all of these are treated as equivalent in AngularJS:
+-
+- ```
+
+  ```
+
+- <span ng:bind="a" ng-bind="a" data-ng-bind="a" x-ng-bind="a">
+- ```
+  */
+  ```
+
+/\*\*
+
+- @ngdoc property
+- @name $compile.directive.Attributes#$attr
+-
+- @description
+- A map of DOM element attribute names to the normalized name. This is
+- needed to do reverse lookup from normalized name back to actual name.
+  \*/
+
+/\*\*
+
+- @ngdoc method
+- @name $compile.directive.Attributes#$set
+- @kind function
+-
+- @description
+- Set DOM element attribute value.
+-
+-
+- @param {string} str1 Normalized element attribute name of the property to modify. The name is
+-          reverse-translated using the {@link ng.$compile.directive.Attributes#$attr $attr}
+-          property to the original name.
+- @param {string} str2 Value to set the attribute to. The value can be an interpolated string.
+- @returns {string}
+  \*/