-
Notifications
You must be signed in to change notification settings - Fork 12.8k
[NewErrors] 5.7.0-dev.20240929 vs 5.6.2 #60095
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
Comments
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
@iisaduan please take a look at e.g. #60095 (comment), I think something happened with your fragment change |
hi @iisaduan |
@robertIsaac The errors should be fixed by 5.7.3. Can you double check what version you are using? |
yes it's 5.7.3 (Same with 5.8) |
I'm taking a look! |
@robertIsaac apologies for the delay in response! The behavior change is intentional, as the 5.7 change was to make fragments type check in the same way, both when written as The definitions in |
Thank you for your time and the explanation |
@robertIsaac actually, it seems typedoc has fixed the issue as of typedoc 0.27.0. Are you able to update? |
I will check it tomorrow |
@iisaduan while there are a lot of breaking changes in 0.26 and 0.27 and I don't have the time now to investigate and fix the breaking changes, I could confirm that updating to 0.27 fixed the problems with the fragment |
The following errors were reported by 5.7.0-dev.20240929, but not by 5.6.2
Pipeline that generated this bug
Logs for the pipeline run
File that generated the pipeline
This run considered 800 popular TS repos from GH (after skipping the top 0).
Successfully analyzed 453 of 800 visited repos
Investigation Status
The text was updated successfully, but these errors were encountered: