Merge studio web into the monorepo itself#72
Conversation
feat(images): add image inputs in studio web
Dev.state fix
|
Basic build and run works well for me - we may wish to include a note to remove |
|
getting a lot of these when running |
I get those errors if I don't first launch Unfortunately, no, I still don't have a single-call command to test web-component... (Well, we do, there's a |
Ah, okay, yes, I have to serve the test data and the web-component (and remember to |
dhdaines
left a comment
There was a problem hiding this comment.
This works at least as well as it did before, I approve
|
To document the general approach used in merging: In a fresh Studio-Web clone: make sure the only changes are a long list of renamed: files. And make sure there are no files left. Go to Web-Component on branch A bunch more adjustments were required, but those are all in separate commits, so see the commit logs for more details. |
I think this is ready to become our new main branch, as is.
Please review but do not merge: I want to do a fast-forward merge from the CLI, any other way to merge this particular PR risks creating an absolute mess of the repo.
Done:
packages/studio-websubdirectoryStill TODO (and I think it's OK to do these after merging the PR):
fix the publication of studio-web to npm from here instead of from the Studio-Web repo(n/a, Studio-Web is deployed, not published)@roedoejet and @dhdaines if you can review this, that would be great, and then I'd like to forward-forward merge this into main soon so future development will continue from here.