This repository has been archived by the owner on May 29, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
3.0-ify shadow-dom, style-shadow-dom, and custom-css-properties #2476
Merged
Merged
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
5be186c
update shadow dom docs for p3 - first pass
5a19243
update style shadow dom part 1
a2321f4
custom style etc
8bba339
custom props update for 3.0
459269a
proofread
d6be16e
proofread
1ebff40
feedback
d9d4ff6
resurrect missing bits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
check this
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.
I don't think this is a valid format.
If the module has a default export (most of ours don't), you can do:
import defaultExport from "module specifier"
To create a new object that contains references to all of the exports from a module, you can do:
import * as myNameforFNO from '@Polymer.../flattened-nodes-observer.js';
Then use myNameforFNO.FlattenedNodesObserver;
Or you could just import individual symbols exported from the module:
import {FlattenedNodesObserver} from 'module specifier';