-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
merge material.angular.io repo #29925
Open
alexeagle
wants to merge
846
commits into
angular:main
Choose a base branch
from
alexeagle:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+64,106
−0
Conversation
This file contains 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
Switches the repo to use eslint instead of the deprecated tslint. Also adjusts the default config to match our previous setup.
i forget we're LLC :)
Updates the Angular packages to v12 RC and sync up the version of MDC.
- needed for `data:image/png;base64` images used in some examples
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 <[email protected]>
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] <[email protected]>
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] <[email protected]>
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] <[email protected]>
- add links for additional help/support resources in homePage - add twitter, angular event and angular blog Fixes angular#133 Co-authored-by: Michael Prentice <[email protected]>
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.
Lately the dependency installs when forking to Stackblitz have been really slow. It seems like switching back to npm speeds them up significantly (from ~5min to ~30s). Also updates the Angular version which has a much smaller bundle size. Note that just doing this didn't help much for yarn which was getting stuck for a long time after the packages are installed.
Updates to Angular 19 in order to fix the deployment job.
…#1270) * refactor: migrate to signal inputs using automated migration Migrates all compatible inputs to signal inputs.
* refactor: switch to signal queries Runs the signal queries migration in this repository. * fixup! refactor: switch to signal queries Fix type * fixup! refactor: switch to signal queries Fix type
Some optional queries were incorrectly marked as required which was throwing runtime errors.
Fixes a lint issue and a type error.
Bumps the docs and the Stackblitz template to the latest versions.
Updates to rxjs 7 to fix the deployment and keep us up to date.
* use mat.theme * update deps * update deps --------- Co-authored-by: Andrew Seguin <[email protected]>
Fixes a few tests that were failing after the standalone switch.
alexeagle
requested review from
crisbeto and
amysorto
and removed request for
a team
October 25, 2024 15:16
angular-robot
bot
added
detected: feature
PR contains a feature commit
area: docs
Related to the documentation
area: build & ci
Related the build and CI infrastructure of the project
labels
Oct 25, 2024
Adds a "Styling" page to each component that tells users how to customize the component's styles.
Fixes the following issues with the styling page: * The table header background wasn't themed correctly. * The filters looked weird on smaller screens. * Filtering was case-sensitive.
renames `test-harnesses` route to `testing` as entry point for `cdk/testing` is latter in packages repository, this was causing links to not work properly when redirected to a route with `test-harnesses`
Fixes that part of the navigation didn't have a background if the links wrap to the next line.
Fixes that the cookie popup didn't have a box shadow. Fixes angular#29958.
Updates the repo to the release candidate of Angular 19.
Fixes that we weren't resetting the `body` element's default `margin` which caused some scenes to have incorrect offets for the overlays.
`ComponentFactoryResolver` isn't necessary anymore so it can be removed.
Sets up a scene for the timepicker that can be used for generating previews.
Exposes the timepicker in the docs.
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: build & ci
Related the build and CI infrastructure of the project
area: docs
Related to the documentation
detected: feature
PR contains a feature commit
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.io
folder.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.