-
Notifications
You must be signed in to change notification settings - Fork 6.8k
build: fix chips drag-drop example not working and improve example-module generation #20003
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
Merged
andrewseguin
merged 2 commits into
angular:master
from
devversion:build/fix-examples-chips
Jul 17, 2020
Merged
build: fix chips drag-drop example not working and improve example-module generation #20003
andrewseguin
merged 2 commits into
angular:master
from
devversion:build/fix-examples-chips
Jul 17, 2020
Conversation
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
crisbeto
approved these changes
Jul 16, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
dcfd965
to
cd05f95
Compare
…dule generation Loading the chips-drag-drop example in the docs site is currently not possible, as the example files fail to load. This is because the example id does not match up with the directory that the example is stored within. This highlights an issue as the docs site assumes a certain folder structure. This is not ideal and an implementation detail specific to the Angular Components repository. The docs site should not need to make any assumptions about where code lives, but instead should just retrieve this information through the example information. That way we are free to change layout/file conventions in the components repository without having to worry about it breaking the docs site. This is implemented as part of this commit. Also a few sanity checks that enforce consistency (for improved code health) have been added. The new concept for examples also allows us to remove empty CSS files for examples without CSS.
We now can have examples without CSS files. This was previously not possible and the docs site just failed loading as it assumed a CSS file per example. We remove those empty stylesheets as they are superflous to examples and rather can confuse/distract the examples in the docs.
cd05f95
to
e506b1b
Compare
ngwattcos
pushed a commit
to ngwattcos/components
that referenced
this pull request
Jul 20, 2020
…dule generation (angular#20003) * build: fix chips drag-drop example not working and improve example-module generation Loading the chips-drag-drop example in the docs site is currently not possible, as the example files fail to load. This is because the example id does not match up with the directory that the example is stored within. This highlights an issue as the docs site assumes a certain folder structure. This is not ideal and an implementation detail specific to the Angular Components repository. The docs site should not need to make any assumptions about where code lives, but instead should just retrieve this information through the example information. That way we are free to change layout/file conventions in the components repository without having to worry about it breaking the docs site. This is implemented as part of this commit. Also a few sanity checks that enforce consistency (for improved code health) have been added. The new concept for examples also allows us to remove empty CSS files for examples without CSS. * chore: remove empty CSS files from examples We now can have examples without CSS files. This was previously not possible and the docs site just failed loading as it assumed a CSS file per example. We remove those empty stylesheets as they are superflous to examples and rather can confuse/distract the examples in the docs.
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
action: merge
The PR is ready for merge by the caretaker
cla: yes
PR author has agreed to Google's Contributor License Agreement
P2
The issue is important to a large percentage of users, with a workaround
target: minor
This PR is targeted for the next minor release
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.
Loading the chips-drag-drop example in the docs site is currently not
possible, as the example files fail to load. This is because the example
id does not match up with the directory that the example is stored within.
This highlights an issue as the docs site assumes a certain folder
structure. This is not ideal and an implementation detail specific to
the Angular Components repository. The docs site should not need to
make any assumptions about where code lives, but instead should just
retrieve this information through the example information. That way we
are free to change layout/file conventions in the components repository
without having to worry about it breaking the docs site.
This is implemented as part of this commit. Also a few sanity checks
that enforce consistency (for improved code health) have been added. The
new concept for examples also allows us to remove empty CSS files for
examples without CSS.