premisedata / dynamic-data-form-extension

Backstage Plugin - Dynamic Data Form Extension (Frontend and Backend Plugins)
Apache License 2.0
6 stars 7 forks source link

candidate.toLowerCase is not a function #23

Open christianherweg0807 opened 3 weeks ago

christianherweg0807 commented 3 weeks ago

Hey. I followed the steps in the README of you dynamic-pick-extension. I created a small template in the Template Editor: `--- apiVersion: scaffolder.backstage.io/v1beta3 kind: Template metadata: name: open-pr-with-business-catalog-entry-product spec: parameters:

TypeError candidate.toLowerCase is not a function

image image

Any clue what I´ve missed?

christianherweg0807 commented 3 weeks ago

My goal is to select GitHub repositorys per dropdown. I think I´ve to use your Backend Plugin for this, right? Is your Plugin already migrated to the new Backend System? In you Readme you have an example with :

form_data: github/teams

You you provide example code for this?

nia-potato commented 2 weeks ago

@nthings hi thanks for the plugin, i am also getting the same error, is there anything we are missing in the setup?

siarheirdn commented 2 weeks ago

same issue :( example is wrong https://www.npmjs.com/package/@premise/plugin-dynamic-pick-extension?activeTab=readme

parameters:
    - category:
        title: Category
        type: string
        ui:field: DynamicPickExtension
        ui:options:
            # IMPORTANT: The endpoint needs to return a JSON array of strings.
            external_data: https://dummyjson.com/products/categories

restApi https://dummyjson.com/products/categories returns list of objects instead of strings. not a bug?

RFackrell commented 1 week ago

Just adding to this. We were using this to query an internal api that was processing some data and serving json arrays more securely. It was working well a couple weeks ago but is now broken.

nia-potato commented 1 week ago

@RFackrell i am trying to do the same, for it hit a internal endpoint with auth, did you have to modify the plugin to use a existing token in the app-config and the fetch it via the backend to access the file? or was it just a json endpoint without auth hosted internally?