[RFC]elements schema: add support for custom schemas
See original GitHub issuein @Compoent
, schemas can currently only use the following values:
CUSTOM_ELEMENTS_SCHEMA
-> allow anycustom-tag
with any property,NO_ERRORS_SCHEMA
-> allow any tag and any property
We need to implement a way to defined custom schemas, ie defining all polymer elements and their properties (and events).
@mprobst when would you be available so that we can discuss how to integrate with the security schema ?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:63
- Comments:40 (12 by maintainers)
Top Results From Across the Web
Custom schemas - dbt Developer Hub
You can use custom schemas in dbt to build models in a schema other than your target schema. It's important to note that...
Read more >Deploy to custom schemas & override dbt defaults - YouTube
In dbt projects with a lot of models, it may be useful to instead build some models in schemas other than your target...
Read more >Create and use custom schemas | Vertex AI - Google Cloud
Use custom schemas to type check metadata properties and to query resources by schema, for example, "list all Artifacts of type MyCustomModel ....
Read more >Custom Schemas - Amazon Cloud Directory
These required fields form your schema's skeleton elements, to which you add your own fields. Map the name and type of each field...
Read more >How to create a custom schema - Supermetrics Support
Use custom schemas across your Supermetrics data transfers, ... Click Save as to save the query and add it to a schema.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This issue has been around since 2016, is not hard to fix and would help EVERY angular project that uses web components. To me it feels like it is strategically ignored to keep up lock in.
is there any reason to not just provide a way to customize the following checks? https://github.com/angular/angular/blob/b5ab7aff433a67cddaa55e621d17b1a1b07b57c2/packages/compiler/src/schema/dom_element_schema_registry.ts#L294 https://github.com/angular/angular/blob/b5ab7aff433a67cddaa55e621d17b1a1b07b57c2/packages/compiler/src/schema/dom_element_schema_registry.ts#L315
if these were pluggable users could already significantly refine which tags to bail out on. this would already be much better than just dropping everything when CUSTOM_ELEMENTS_SCHEMA is used
if i patch my local compiler with 3 lines i can get immediately it to do what i need!