merge material.angular.io repo#29925
Merged
josephperrott merged 852 commits intoangular:mainfrom Dec 18, 2024
Merged
Conversation
When generating an example in Stackblitz, we have to create a `form` element and submit it to a specific URL. The `form` has to be created eagerly, because some browsers will block us from submitting it if it is created asynchronously. As a result of this setup we fire off a lot of HTTP requests when an example is rendered which slows the page down a lot. These changes make the following improvements which shave off more than a second of scripting time when transitioning from the "Overview" to "Examples". I've used the datepicker examples as a benchmark. 1. Runs the HTTP requests outside of the Angular zone so that we don't trigger change detections once each request is resolved. 2. Caches the file content so that the user doesn't have to load the same file multiple times. I've also fixed that the copyright still said "2020".
- fixes ng serve warnings about server via workspace migration
- fixes a bug in sidenav where user has to scroll to bottom of the page to reach bottom of navigation Fixes angular#857 Co-authored-by: Michael Prentice <splaktar@gmail.com>
Bumps [lodash](https://github.com/lodash/lodash) from 4.17.20 to 4.17.21. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](lodash/lodash@4.17.20...4.17.21) Signed-off-by: dependabot[bot] <support@github.com>
Bumps [underscore](https://github.com/jashkenas/underscore) from 1.12.0 to 1.13.1. - [Release notes](https://github.com/jashkenas/underscore/releases) - [Commits](jashkenas/underscore@1.12.0...1.13.1) Signed-off-by: dependabot[bot] <support@github.com>
Bumps [url-parse](https://github.com/unshiftio/url-parse) from 1.4.7 to 1.5.1. - [Release notes](https://github.com/unshiftio/url-parse/releases) - [Commits](unshiftio/url-parse@1.4.7...1.5.1) Signed-off-by: dependabot[bot] <support@github.com>
- add links for additional help/support resources in homePage - add twitter, angular event and angular blog Fixes angular#133 Co-authored-by: Michael Prentice <splaktar@gmail.com>
Exposes the docs for `cdk/coercion` and `cdk/collections`. Fixes angular#19530. Fixes angular#18818.
Replaces the `async` method marker with a generic marker that can also be used for static methods. Related to angular#22786.
Due to legal requirements we have to have a cookie disclaimer popup. It is always shown until the user agrees to it. After the user has agreed, the popup won't be shown on subsequent sessions. Fixes angular#22746.
Currently we fetch a doc every time we need to display it which means that user navigating between two pages will have to request the same information multiple times. These changes add a caching layer since the information isn't going to change.
Follow-up to angular#22829. Exposes the CDK accordion docs in the navigation.
Fixes that the guide tiles can overlap the footer on smaller screens. Fixes https://github.com/angular/components/issues/22860.
Co-authored-by: Michael Prentice <splaktar@gmail.com>
- fix cookies dialog button contrast in dark mode Fixes angular#1008
Currently the carousels on the front page don't align with any other elements on the page which looks odd. This seems to be due to a limitation where the item size has to be passed in to the carousel. These changes reimplement the carousel, making it more flexible and allowing it to handle any size of items and any spacing. The new carousel is used on the frontpage to lay out the items in a way that aligns with the rest of the content.
…1004) - fix hover and focus indicators on header nav items to have sufficient contrast Fixes angular#759
Updates the styling page to account for a change in the token docs format. Also outputs the example as HTML since it is now syntax-highlighted.
* add system variables guide * use static style bindings --------- Co-authored-by: Andrew Seguin <andrewseguin@google.com>
Updates the repo to the stable version of Angular 19.
Hides the styling page for the ripple since it's part of `core`. Fixes angular#30098.
previously we weren't showing any other information other than `breaking-change` for deprecated fields, this commit adds a component that protrays information regarding deprecation in tooltips rather than `title` attribute closes angular#29839
Member
|
Heads-up that I had to merge in one more PR to fix the docs site deployment: angular/material.angular.io#1297 |
Updates to the latest `next` version to unblock the deployment of the docs site.
Contributor
Author
|
@crisbeto no worries I've just freshly merged the HEAD of each repo: |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Used git-filter-repo to rewrite history, so commits appear to have always been beneath the
material.angular.iofolder.Follows https://blog.aspect.build/otherrepo-to-monorepo
Note, this MUST be a merge commit so care should be taken when merging to prevent squashing the history and losing the git blame layer.