weird duckDb unnesting thing

example.json

{"origRow": 1, "foo":42,"bar":"fortyTwo","myNest":[{"hello":"space","goodbye":"world"},{"hello":"time","goodbye":"gravity"}]}
{"origRow": 2, "foo":420,"bar":"fortyTwenty","myNest":[{"hello":"you","goodbye":"me"},{"hello":"we","goodbye":"thee"}]}

stuff.sql

CREATE OR REPLACE VIEW temp_view AS
WITH MY_FUN_TABLE AS (
    SELECT
        *
    FROM
        read_json('/Users/ak/Desktop/example.json', 
        format = 'newline_delimited',
        auto_detect = TRUE
    )
),

MY_WEIRD_SCHEMA AS ( 
    SELECT 
        origRow,
        foo,
        bar,
        something.*,
        -- ▲  the ONLY way TO access our 'exploded' json 
        -- ▼  is with the 'unnest' prefix?
        unnest.hello,
        unnest.goodbye
        -- something.hello -- fails: Binder Error... but WHYYY????
    FROM 
        MY_FUN_TABLE AS T,
        UNNEST(T.myNest) AS something -- this ends up being named "unnest" despite the alias ... and you can't change it!
)
SELECT * FROM MY_WEIRD_SCHEMA;

DESCRIBE temp_view;

👋 i am trying to understand why using UNNEST() to explod loaded JSON data does not support aliasing with AS (like you might expect) ... so i can't UNNEST(table.column) AS foo and then foo.bar ... i have to unnest.bar ?

check out the schema of this view: