basset | A better asset management package for Laravel | Web Framework library

You are referring to the names as identifiers and not as constants like you want them to be. Change Wagner to "Wagner" for example. You get an error because these identifiers were never defined before being used by you.

Also, right now when you are comparing the strings you are comparing their addresses in memory. Consider using strcmp if you want to compare the strings and not their addresses.

input_dict_of_list["pets"] is a list. This list contains 6 items, which can be accessed as input_dict_of_list["pets"][0], input_dict_of_list["pets"][1], ..., input_dict_of_list["pets"][5].

The names of the breeds can be accessed as input_dict_of_list["pets"][0]['breed'], input_dict_of_list["pets"][1]['breed'], ..., input_dict_of_list["pets"][5]['breed'].

Or you can iterate over the items in this list using a for-loop:

Try this

A few little things need to be changed in your code. Below is your code with my corrections. Explanations after the code.

The word return is missing in the "getBreed" method

Spacy NER model training includes the extraction of other "implicit" features, such as POS and surrounding words.

When you attempt to train on single words, it is unable to get generalized enought features to detect those entities.

Take, for instance, this example extracted from Spacy's own training tutorial:

Look at the response structure carefully. These will work:

You are calling your find_pet_by_name(shop) method here:

I don't think there is any way for a Function to know if an Alias has been used, but the point is it shouldn't matter. Inside the function you should always refer to the parameter as if its used by it's primary name.

If you need the parameter to act different depending on whether it's used an Alias that is not what an Alias is for and you should instead use different parameters, or a second parameter that acts as a switch.

By the way, if you're doing this because you want to use multiple parameters as ValueFromPipelineByPropertyName, you already can with individual parameters and you don't need to use Aliases to achieve this.

Accepting value from the pipeline by Value does need to be unique, for each different input type (e.g only one string can be by value, one int by value etc.). But accepting pipeline by Name can be enabled for every parameter (because each parameter name is unique).