Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge EFv2 work to main #5798

Open
wants to merge 267 commits into
base: main
Choose a base branch
from
Open

Merge EFv2 work to main #5798

wants to merge 267 commits into from

Conversation

tjprescott
Copy link
Member

@tjprescott tjprescott commented Jan 28, 2025

Closes #5788.

TODO

  • Moving EFv2 package into main branch.
  • Set up workspace and publishing pipeline
  • Add "highly experiemental" warning message. Question: on installation or emission?

import { isTemplateInstance } from "../../../core/type-utils.js";
import { Enum, Interface, Model, Scalar, Union } from "../../../core/types.js";

export function getPlausibleName(type: Model | Union | Enum | Scalar | Interface) {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bterlson it seems strange to have this free-floating method here. Isn't that what typekits were created to alleviate? Should this be relocated somewhere or is it fine as-is?

namespaces: Namespace[];
}

export class TypeCollector {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bterlson I think this was some work I had originally done long ago and doesn't really have anything to do with EFv2. Shall I remove it?

} from "@typespec/compiler";
import { $ } from "@typespec/compiler/typekit";

export function isModel(type: any): type is Model {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bterlson are these intended to work with typekits, or are these like an ancestor of them? Basically, should I keep these in or remove them?

@@ -0,0 +1,56 @@
{
"name": "@typespec/http-client-library",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bterlson are you okay with renaming this http-client?

packages/http-client/package.json Show resolved Hide resolved
packages/http-client/package.json Outdated Show resolved Hide resolved
@tjprescott tjprescott marked this pull request as ready for review January 29, 2025 17:54
@tjprescott tjprescott changed the title IGNORE: Merge EFv2 to main Merge EFv2 work to main Jan 29, 2025
@tjprescott tjprescott force-pushed the efv2merge branch 2 times, most recently from 3d55dfb to 51c68b5 Compare January 29, 2025 22:50
@@ -0,0 +1 @@
export * from "./kits/index.js";
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bterlson should this live in an "experimental" folder and namespace like it does for compiler and http?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Moving EFv2 in microsoft/typespec main branch and set up publishing
6 participants