-
Notifications
You must be signed in to change notification settings - Fork 51
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
Adding typespec-azure-portal-core package #224
Conversation
! Conflicts: ! pnpm-lock.yaml
! Conflicts: ! pnpm-lock.yaml
…espec-azure into yejeelee/azurePortal ! Conflicts: ! pnpm-lock.yaml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this package make sense to be used in the azure playground? If so, you should also update the playground config in packages/typespec-azure-playground-website/src/index.ts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I should cover this in next iteration :) is that okay with you?
…espec-azure into yejeelee/azurePortal
export * from "./keys.js"; | ||
export { $lib } from "./lib.js"; | ||
export * from "./types.js"; | ||
export * from "./validate.js"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
export * from "./validate.js"; | |
export {$onValidate} from "./validate.js"; |
try to limit what you export as everything becomes public api for your package and change will break users
Double check for the other export *
if you do actually want that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah! I see yes checked everything will be needed
No description provided.