Access to Structure Item Value on Plugin

Kirby 3 Questions 🤔
1

So I started to make new custom field that works in structure field and so newby in Vue.

How can i access to structure item value that same index?

Following example, i need to “Need Access Field” value from “My Custom Field”:

ss
ss.png1420Ă—188 4 KB

What’s the trick?
Thanks

2

I made a little progress in Vue :partying_face: But i stacked on options :pensive:

In my plugin, i’m trying to load dynamic options from custom endpoint url and succeeded in this like following mounted() method:

Here my mounted() function:

mounted() {
    var self = this;
    const csrf = panel.csrf;

    fetch(panel.api + '/api/test', {
        method: "GET",
        headers: {
            "X-CSRF": csrf
        }
    }).then(function (response) {
        return response.json();
    }).then(function (data) {
        self.options = data;
    }).catch((error) => {
        console.log(error);
    });
}

11152206-e890-4c3a-ybcf-6209054d7fd2
11152206-e890-4c3a-ybcf-6209054d7fd2.gif1170Ă—400 475 KB

All loaded options disappearing after selected/added any option like screencast.

Where am I doing wrong?

3

Is there anyone have an idea? :pray:

4

Could you post the whole component?

5

Sure, thank you in advance

Vue index.js

https://jsfiddle.net/r5a1we09/

Blueprint

attName:
    label: Att Name
    type: text
    width: 1/4

attValues:
    label: Att Values
    type: tagsrelated
    width: 3/4
    api: /products/attributes
    related: attName

Btw, options are loading correctly when i opened the structure item after save/cancel.
Only disappearing after select a tag.

6

Solved with watch() method as load options each event on value like that:

watch: {
    value(value) {
        this.fetchOptions();
    }
}
mounted() {
    this.fetchOptions();
},
methods: {
     fetchOptions(options) {
        // load options
     }
}
7 
'extends' => 'tags',    // index.php
 extends: "k-tags-field", // index.js
 extends: 'k-tags-input', // index.js

I made this plugin with extends the tags plugin, but why is the core tags plugin affected with this extending?

What do I have to do to keep core fields from getting affected?