-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Improve components infrastructure #12145
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
Conversation
Ahhhhh I see, if there are file conflicts, a build will not be triggered. But you won't know about the conflict until you mark the PR as ready to review. In any case, the PR is NOT ready for review but I'll ping when I figure this out. |
@rynowak Anyone who can help me debug TS test failures? I'm seeing the following error but I'm not quite sure how I caused it:
|
I can help with that - do you have the contents of the page? |
@JunTaoLuo Could you describe what these changes do? I see there are many changes in |
Could you clarify why we're still going with a design like that? In what cases is it useful for |
src/Components/Blazor/testassets/HostedInAspNet.Client/HostedInAspNet.Client.csproj
Outdated
Show resolved
Hide resolved
This is just working around the issue
I still see a failure on macOS. Seems pretty consistent at this point (3/3) |
@JunTaoLuo If it gets to the point where that's the only thing blocking this PR, then please skip that one test (might have to comment it out, not sure what other mechanism exists for Jest tests) and file an issue for us to investigate it. There is a possibility we actually have a product bug on Mac so we'd definitely want to investigate it ASAP. |
Okay, I'm going to disable it. |
I'll merge pending approval @dougbu |
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.
One definite deletion and this is ready to go
// expect(testDisplay.show).toHaveBeenCalled(); | ||
// expect(testDisplay.failed).toHaveBeenCalled(); | ||
// expect(reconnect).toHaveBeenCalledTimes(3); | ||
// }); |
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.
Don't check in commented-out code. This can be found in previous commits if needed in the future.
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.
This is tracked by #12578. I would rather add a comment explaining why this is commented out rather than delete the actual test code. Though I don't feel strongly. @SteveSandersonMS ?
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.
Commenting this out is the closest thing we have to a [Skip]
attribute. It will be uncommented soon, so as long as there is a comment at the top explaining why this is here, and linking to the issue #12578, I think it's a fair way to express the same intent as [Skip]
.
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.
Have you tried it.skip(...)
?
src/SignalR/clients/ts/FunctionalTests/SignalR.Npm.FunctionalTests.npmproj
Outdated
Show resolved
Hide resolved
This comment was made automatically. If there is a problem contact [email protected]. I've triaged the above build. I've created/commented on the following issue(s) |
This reverts commit e149f9c.
…#12744) * Revert "Revert "Improve components infrastructure (#12145)" (#12679)" This reverts commit e2d57e2. The improvement to components infrastructure is now reinstated with the following changes: * Check in release JS artifacts and use them as a fallback when it's not possible to build npmproj. * Dont' build nodejs in source build.
Addresses #12030
A few of the workflows I'm trying to improve:
#11592 Stop checking in JS artifacts from Web.JS in Components and compile the artifacts at build time. I need to check that relying on yarn is compatible with source build
Able to trigger builds of Web.JS from depending projects
./build.cmd in Components dir should succeed if yarn is installed