Compatibility with Typespec Emitters V2

[bZichett]

Is this library deprecated? Was interested in trying it out but is out of date and uninstallable with V2 emitters.

[xferra]

@bZichett I encountered the same issue.
You can check out a quick (and untested) fix here: xferra@105a48e

[bZichett]

Interesting. Reviewed the commit real quick - any chance it's an LLM patch (responding specifically to "untested")? If so curious what context you gave it - as it is working as is at least for basic cases. There are a few curious lines in the changelog that I've decided are worth further investigation (especially if LLM, but less so if you looked into it yourself)

If you went ahead and worked on it without LLM (or even with LLM) thank you, kindly dear @xferra

I pulled your branch, tsc compiled it, pointed to it via relative directory, marked a model with an entity decorator doing a quick test on a single model - and it successfully output what I expected.

I wanted to see if my schema as is could be casted without error - one expected error where it doesnt support numeric enums came up immediately. In any case, my result is below (shortened) just as a basic exemplar show casing typespec basics (composition.) Note: My classes can be much longer than this though and I don't have a full output (various errors mostly due to enums and relationships I need to wire up with entity() decorators)

I'd like to see if I can use this approach (typespec) as a shared place to then extend how the API handles the same models - then I can have a single source of truth that can generate code as server handler stubs, client api and finally this piece: postgresql schema (table defs, not queries or other things not supported by typespec emitter - there is a lot still)

/**
 * UUID scalar type
 */
@format("uuid")
scalar uuid extends string;

model UUIDModel {
  @format("uuid")
  uuid: uuid;
}

model IDModel {
  @key
  id: ModelId;
}

model TimestampFields {
  created: utcDateTime;
  modified: utcDateTime;
}

@entity()
model Node {
  ...utils.IDModel;
  ...utils.UUIDModel;
  ...TimeFields;
  text_json?: Record<unknown>; // Piece type - JSON representation of rich text;
  deleted?: boolean;
 ...
}

CREATE TABLE Node (
    id INTEGER PRIMARY KEY,
    /* UUID scalar type */
    uuid UUID NOT NULL,
    created_at TIMESTAMP WITH TIME ZONE NOT NULL,
    updated_at TIMESTAMP WITH TIME ZONE NOT NULL,
    text_json JSONB,
    deleted BOOLEAN
   ...
};

[xferra]

@bZichett Many thanks!

By “untested” I just mean I only tried some simple cases, and it works fine for my models. npm run test fails (which is expected since the versioning part was removed), so there might still be issues in other scenarios.

I used an LLM to get an overview of the code structure, but it wasn’t very helpful for making the actual changes.