Draft
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Porting the component select twig component over to the new world.
Don't let the component fool you, this (currently draft) PR also takes some steps towards bringing the component system into PHP. At the end of the day (at least until we're full inertia, but maybe forever) we'll likely have two component sets. Vue and PHP. The purpose of this layer is to abstract some of the fiddly bits of dealing with the web components that power the actual UI. The web components will control the style and functionality of the components while the PHP and Vue layers provide an abstraction that make them easier to use in those contexts.