Merged
Conversation
When creating a form blueprint, the **name matters**. For example `header.some.thing`.
That makes impossible to reuse named fields.
Let's say a plugin defines such a `foobar` field:
```yaml
# blueprints.yaml
form:
validation: strict
fields:
foobar:
type: select
label: Default value if not overriden per-page
data-options@: '\Grav\Plugin\MyPlugin::foobar'
```
But such value can be override on a page basis. The best is to reuse already defined blueprint:
```yaml
# blueprints/modular/form.yaml
form:
fields:
# importing blueprint admin fields for per-page override
import@:
type: blueprints.yaml:form/fields # <-- this syntax is horribly difficult to deduce and undocumented
context: plugins://myplugin
# and override
enabled: { unset@: true } # sure, this is not needed
# `foobar` is not ok, in this context we must use `header.form.foobar`
foobar:
replace-name@: true
name: header.form.foobar
```
Author
|
ping |
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
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 creating a form blueprint, the name matters. For example
header.some.thing.That makes impossible to reuse named fields.
Let's say a plugin defines such a
foobarfield:But such value can be override on a page basis. The best is to reuse already defined blueprint:
See also: #23