Skip to content

feature: bind-attributes & bind-xyz

Jean-Baptiste Pasquier requested to merge feature/bind-attributes into master

New feature: bind-attributes and bind-xyz.

Usage

With a container

<solid-display
data-src="/examples/data/users.jsonld"
bind-attributes
fields="first_name, text, other_user_first_name"
value-text=" likes "
bind-value-other_user_first_name="first_name">
</solid-display>

When visiting /path/to/file/@%2Fexamples%2Fdata%2Fuser-1.jsonld@ will display every user's first name, and all of them will like user-1!

With a resource

<solid-display
data-src="/examples/data/user-2.jsonld"
bind-attributes
fields="first_name, text, other_user_first_name"
value-text=" likes "
bind-value-other_user_first_name="first_name">
</solid-display>

When visiting /path/to/file/@%2Fexamples%2Fdata%2Fuser-1.jsonld@ will display user-2 first name and he will like user-1!


Includes

  • bind-attributes
  • bind-xyz, xyz can be anything, even something not managed by a startin'blox component
  • tests fix: Core version 0.14? 🎉 + Path to examples + sib context
  • test case for both a container and a resource

Improve me one day

  • The binded attribute can only be sourced from a single resource, not a container. (Enum maybe?)
  • Those populate shouldn't be required. Bug core? Whenever a value-xyz is modified it does not populate the related solid-display.

Merge request reports