Handle vendor namespaces and handle for blueprints and fieldsets #310
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
|
After this update, fieldsets that are exported by vendor:publish from third-party packages are broken
|
Contributor
Author
|
@lazerg what is the handle of fieldset in the database? |
|
after update it is similar to second one format, but
|
Contributor
Author
|
@ryanmitchell Yes ! |
Contributor
Author
|
Thanks for confirming, I'll bundle it into the next release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When importing add-on namespaced field sets and blueprints from the stache the namespace (for blueprints) is prefixed with vendor, and for field sets the handle is prefixed too.
This PR updates the logic to handle those appropriately.