@source inline() not work as expected

[WishKwok]

i create a @Utility

@utility btn-* {
    --btn-theme: --value(--color-*-500);
    --btn-theme-light:--value(--color-*-400);
    --btn-theme-dark:--value(--color-*-500);
}

i want to @source inline it

@source inline("btn-primary");
@source inline("btn-gray");
@source inline("btn-blue");

then, I have discovered a problem.
Only when I fully define these variables in my custom @theme will it work, even if these variables already exist in the default @theme.

// my custom
    --color-primary: oklch(33.586% 0.11847 256.84);
    --color-primary-400: oklch(62.396% 0.20494 256.67);
    --color-primary-500: oklch(54.12% 0.20386 258.39);
// default ,but i deliberately included it.
    --color-gray: oklch(96.415% 0 none);    
    --color-gray-400: oklch(72.516% 0 none);
    --color-gray-500: oklch(64.341% 0 none);
 // default
    /*--color-blue: oklch(33.586% 0.11847 256.84);*/
    /*--color-blue-500:oklch(14.539% 0.03805 246.79);*/
    /*--color-blue-400:oklch(14.539% 0.03805 246.79);*/

compiled result

blue is overlook。
And I found that even if it was directly written in the HTML, this @Utility still didn't work.
I don't know if this is its normal operating mechanism or if I have done something wrong.

[wongjn]

I'm not sure if it is intended to work when you have the asterisk in the middle of a the theme token namespace. All examples in the docs show it at the end:

@utility tab-* {
  tab-size: --value(--tab-size-*);
}

Though it is curious that it works if you define the CSS variables in your own @theme.

[WishKwok]

I once doubted that it was the case, but the actual situation is that it can work.
I think it might be that it only scans the user-defined @theme content during compilation, but I'm not sure if this is a bug or if it has always worked like this.
If it's not considered a bug, I hope it can be improved.
Thank you for your suggestion.

[WishKwok]

You are correct！🤣
It only matches the string before *. If it doesn't exist, it will not be compiled. 😰
However, the framework itself does not contain --color-xx, so it has been failing all along!!
so i have to type all the --color-xx in @theme.

--color-red: oklch(63.7% 0.237 25.331);
    --color-orange: oklch(70.5% 0.213 47.604);
    --color-amber: oklch(76.9% 0.188 70.08);
    --color-yellow: oklch(79.5% 0.184 86.047);
    --color-lime: oklch(76.8% 0.233 130.85);
    --color-green: oklch(72.3% 0.219 149.579);
    --color-emerald: oklch(69.6% 0.17 162.48);
    --color-teal: oklch(70.4% 0.14 182.503);
    --color-cyan: oklch(71.5% 0.143 215.221);
    --color-sky: oklch(68.5% 0.169 237.323);
    --color-blue: oklch(62.3% 0.214 259.815);
    --color-indigo: oklch(58.5% 0.233 277.117);
    --color-violet: oklch(60.6% 0.25 292.717);
    --color-purple: oklch(62.7% 0.265 303.9);
    --color-fuchsia: oklch(66.7% 0.295 322.15);
    --color-pink: oklch(65.6% 0.241 354.308);
    --color-rose: oklch(64.5% 0.246 16.439);
    --color-slate: oklch(55.4% 0.046 257.417);
    --color-gray: oklch(55.1% 0.027 264.364);
    --color-zinc: oklch(55.2% 0.016 285.938);
    --color-neutral: oklch(55.6% 0 0);
    --color-stone: oklch(55.3% 0.013 58.071);

Then,Success!!

But to be honest, it should have indicated the content that was not generated and the reasons for that.
This experience was a bit hard.
Thank you again for your ideas!!