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

Cleanup MRL / standardize more #1091

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

Cleanup MRL / standardize more #1091

wants to merge 9 commits into from

Conversation

ericanderson
Copy link
Member

@ericanderson ericanderson commented Jan 13, 2025

Cleanup MRL / standardize more

In commit order:

Wonky Codegen for e2e.test.foundry-sdk-generator

The existing code generated into the src which then required us to special case not including it in the tsc output. This was unnecessary and caused special casing in mrl that we could cleanup. We now expect codegen will go into either or both: ./build/codegen and ./src/generatedNoCheck.

Codegen

Just regenerating packages/e2e.sandbox.todoapp/src/generatedNoCheck2 with extensions

Proper extensions for e2e.sandbox.todoapp

Manually renaming remaining extensions in imports

Refactor widget.vite-plugin to use standard paths

Drops a special snow flake tsconfig file. Produces output in a standardized location for turbo.

MRL applied boilerplate

I committed this prior to the MRL changes so that there would be no errors in lint-staged. This is just MRL applied changes for the next commit

Standardize vite apps

Break out 5 projects from nonStandardPackages into viteApp and usesReact. Updates turbo.json with better defaults for the inputs and outputs of the build task and adds comments explaining why things are there.

Remove foundry-sdk-generator from snowflakes

Following the first commit and other prep work, this commit makes all consumer facing cli apps act the same. Notably this means must use exact version matches (this helps prevent surprises for us) just like foundry-sdk-generator used to do. We also had special casing for consola in our tests but it didn't wire up to anything so was pointeless

Empty changeset

There isn't really anything to report here.

@ericanderson ericanderson changed the title Remove special case for wonky test codegen Cleanup MRL / standardize more Jan 13, 2025
const consumerCliPackages = [
"@osdk/cli",
"@osdk/create-app",
"@osdk/foundry-sdk-generator",
];

const testWithHappyDomPackages = [
const viteApp = [
Copy link
Contributor

Choose a reason for hiding this comment

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

When we move widgets out or want to make more sample apps in other repo's, we'd have to update these first? When we move the MRL config out, is it somehow possible to make these inputs of some sort so these names come from the repos that the packages live in themselves?

Copy link
Contributor

Choose a reason for hiding this comment

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

For both this var and others

Copy link
Member Author

Choose a reason for hiding this comment

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

This file is part of a temporary state. The goal will be to refactor this whole file to be a "library" where individual repos would "configure" it with the packages in their own repo that fit the various archetypes.

nihalbhatnagar
nihalbhatnagar previously approved these changes Jan 14, 2025
* origin/main:
  Fixes infinite redirect issue on some errors in the OAuth flow (#1089)
  Tighten return types (#924)
  Add typed lint checks and fix promise related things (#1081)
  Version Packages (beta) (#1090)
  Export hydrateObjectSetFromRid from internal (#1087)
@policy-bot policy-bot bot dismissed nihalbhatnagar’s stale review January 14, 2025 15:10

Invalidated by push of c6fe2de

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.

2 participants