Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Find an alternative to using .type to validate element instances are from this project #87

Open
thure opened this issue Apr 13, 2022 · 0 comments
Open

Find an alternative to using .type to validate element instances are from this project #87

thure opened this issue Apr 13, 2022 · 0 comments
Labels
enhancement New or changed functionality
Milestone
tdp pattern parity

Comments

@thure
Copy link
Contributor

thure commented Apr 13, 2022

If a developer creates a component that returns a Fluent Blocks element, it fails validation since its .type is whatever the developer named the component.

Rather than failing, Fluent Blocks should accommodate this scenario.
@thure thure added the enhancement New or changed functionality label Apr 13, 2022
@thure thure added this to the tdp pattern parity milestone Apr 13, 2022
@thure thure mentioned this issue May 31, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New or changed functionality
Projects
None yet
Milestone
tdp pattern parity
Development

No branches or pull requests
1 participant
@thure