getgrav / getgrav/grav-plugin-admin

dot in blueprint key

Open
#2,280 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
PHP
Stars
377
Forks
225
Avg merge
11h 51m
Merged PRs (30d)
4

Description

i’m making a blueprint for collections for `@page.page`s only, as a `list` field like so:
```yaml
header.content.items:
type: list
fields:
.@page.page:
type: pages
```
but this produces:
```yaml
content:
items:
-
'@page':
page: /slug
```
which then doesn’t work for the templates.

i’ve tried different ways of escaping it, getting different results, but none of them working. a couple of examples:
- `.'@page.page'`:

```yaml
content:
items:
-
'''@page':
'page''': /slug
```
- [`.'[@page.page]'`](https://stackoverflow.com/questions/34070987/escaping-a-dot-in-a-map-key-in-yaml-in-spring-boot):

```yaml
content:
items:
-
'''[@page':
page: /slug
```
- `.[@page.page]`:

```yaml
content:
items:
-
'[@page':
page: /slug
```

doing it as a single value field, with `header.content.items.@page.page` / `header.content.items[@page.page]`, gives similar results.

is this the intended behavior? is there a way to achieve this, or a workaround?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.