The token browser, especially on the Token help page, can quickly get bloated and become hardly understandable. This is becoming especially true with #2621598: Add support for field properties, as several new token types are created. We should introduce an attribute similar to the actual restricted one, to prevent specific nested tokens from being displayed as top-level tokens on the token browser.

For instance, there is not really any point in showing the Array token on the token browser as a top-level token. It should only show up nested under other tokens.

This patch introduces the necessary changes and make Array token nested to illustrate a use case of this.

CommentFileSizeAuthor
#2 some_nested_tokens-2760315-2.patch8.19 KBBambell
nested-tokens-should-1.patch8.19 KBBambell
nested-tokens-after.png252.07 KBBambell
nested-tokens-before.png220.82 KBBambell

Comments

Bambell created an issue. See original summary.

Bambell’s picture

Bambell commented
StatusFileSize
new some_nested_tokens-2760315-2.patch8.19 KB

Same as "nested-tokens-should-1.patch", just so test bot is triggered.

  • Berdir committed 2f1c34b on 8.x-1.x authored by Bambell 
    Issue #2760315 by Bambell: Some nested tokens should not show as top-...
berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Needs review » Fixed

Thanks, looks good.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.