Skip to content

chore: effectively use tasty-inspector in scaladoc#22803

Closed
hamzaremmal wants to merge 1 commit intoscala:mainfrom
hamzaremmal:use-actual-tasty-inspector
Closed

chore: effectively use tasty-inspector in scaladoc#22803
hamzaremmal wants to merge 1 commit intoscala:mainfrom
hamzaremmal:use-actual-tasty-inspector

Conversation

@hamzaremmal
Copy link
Copy Markdown
Member

This partially reverts #21929's fix but keeps the tests that were introduced

This partially reverts scala#21929's fix but keeps the tests that were introduced
@hamzaremmal hamzaremmal self-assigned this Mar 14, 2025
@jchyb
Copy link
Copy Markdown
Contributor

jchyb commented Mar 14, 2025

I believe the underlying problem there was the fact that we didn't pass the settings from the scaladoc Context to the underlying tasty-inspector Context (and going back to just reusing the Context was a quick fix for that, since we wanted to fix the regressions). Also the test I ended adding is an sbt-scripted test, not the scaladoc test (so watch out for that)

@Gedochao
Copy link
Copy Markdown
Contributor

@jchyb @hamzaremmal can we close this? At a glance, it feels like we no longer want to revert the fix?

@Gedochao Gedochao added the stat: stale PR Marks any stale PRs, if no response is given, the PR qualifies as a one to close. label Feb 19, 2026
@Gedochao
Copy link
Copy Markdown
Contributor

Closing due to inactivity.
Feel free to reopen or open another approach.

@Gedochao Gedochao closed this Feb 23, 2026
@hamzaremmal
Copy link
Copy Markdown
Member Author

At a glance, it feels like we no longer want to revert the fix?

Well, it was a dirty fix done there. The idea here is to get rid of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stat: stale PR Marks any stale PRs, if no response is given, the PR qualifies as a one to close.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants