Giters
webcomponents
/
custom-elements-manifest
A file format for describing custom elements
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
350
Watchers:
40
Issues:
76
Forks:
26
webcomponents/custom-elements-manifest Issues
Access modifier issue on derived class
Closed
2 months ago
Comments count
1
Allowed children for slots
Updated
2 months ago
Comments count
6
Needed styles for elements
Updated
2 months ago
Comments count
4
Publish New Version
Closed
2 months ago
Comments count
1
`tagName` should not be part of the manifest
Closed
9 months ago
Comments count
4
Package name field
Updated
2 months ago
Comments count
1
Add support for CSS CustomState
Closed
2 months ago
Add support for enum Values in Attributes/Properties
Updated
5 months ago
Comments count
13
[Proposal] Extend the `type` object with more detailed information
Updated
9 months ago
Comments count
4
Ability to document type of detail property for CustomEvents
Updated
9 months ago
Comments count
5
README should mention that manifest can (and should) be generated by a tool
Updated
a year ago
add funding links
Closed
a year ago
Add support for including canonical URLs for References
Updated
a year ago
Add support for symbol-named class members
Updated
a year ago
Comments count
1
Add support for package and element icons and screenshots
Updated
2 years ago
Comments count
1
Custom Element Status
Updated
2 years ago
Comments count
2
CssCustomProperty should have an inheritedFrom field.
Updated
2 years ago
Comments count
1
sync between source and manifest
Updated
2 years ago
Comments count
2
Publish latest iteration to NPM
Closed
2 years ago
Comments count
4
To which files should the manifest link. .ts, .js, both, ...
Closed
2 years ago
Comments count
8
Example string for a component
Updated
2 years ago
Comments count
1
look for similarities with web-types
Closed
2 years ago
Comments count
1
Deomnstration Project using the Manifest...
Updated
2 years ago
Comments count
1
componentRegistered Information
Closed
2 years ago
Comments count
1
Generated schema contains errors
Closed
2 years ago
Comments count
3
Is WebComponent a Container for other Elements (low prio)
Updated
2 years ago
Comments count
6
Add a Option, to mark the "default" Binding Property or Attribute (low prio)
Updated
2 years ago
Comments count
5
How to output `oneOf` for discriminated unions.
Closed
2 years ago
Comments count
1
Status of the "manifest"
Closed
2 years ago
Comments count
4
desc.startsWith is not a function
Closed
2 years ago
Comments count
2
Samples
Closed
3 years ago
Hint on `Type` for type of type (e.g. 'typescript', 'flow')
Updated
3 years ago
Comments count
1
clearly define Path
Updated
3 years ago
Comments count
1
I expected to see a sample custom-elements.json
Closed
3 years ago
Comments count
4
Add a meta tag to indicate custom elements manifest location on webpage
Updated
3 years ago
Comments count
5
deprecated flag
Closed
3 years ago
Comments count
1
Spread parameters
Closed
3 years ago
Comments count
9
Duplicate attributes when annotating
Closed
3 years ago
Comments count
2
Multiple defaults for CSS Custom Properties
Updated
3 years ago
Comments count
15
No mention of `formAssociated` in schema
Closed
3 years ago
Comments count
2
Publish to SchemaStore.org
Updated
3 years ago
Add InterfaceDeclaration
Updated
3 years ago
link events and attributes/properties
Updated
3 years ago
Comments count
3
Add support for typed Custom CSS Properties
Closed
3 years ago
Comments count
1
Provide a field with the actual class name of a default exported class
Closed
3 years ago
Comments count
5
Add a field for "elementVersion"?
Updated
3 years ago
Comments count
6
Using export map instead of custom property in `package.json`
Closed
3 years ago
Comments count
2
TypeScript error: "tagName" does not exist in type 'ClassDeclaration'
Closed
3 years ago
Comments count
2
Property/Attribute Lifecycle description
Updated
3 years ago
Add recommended JSDoc tags
Updated
3 years ago
Comments count
4
Previous
Next