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

Don't mark wikitext API used by LSP4E as internal #523

Merged
merged 1 commit into from May 10, 2024

Conversation

akurtakov
Copy link
Contributor

In versions 3.x this was api and internals are well hidden (esp in markdown plugin) thus the change to make everything internal was excessive and generates "Discouraged access" issues in LSP4E.

In versions 3.x this was api and internals are well hidden (esp in
markdown plugin) thus the change to make everything internal was
excessive and generates "Discouraged access" issues in LSP4E.
@akurtakov
Copy link
Contributor Author

It was identified that lsp4e is not using latest wikitext - eclipse-cdt/cdt#779 . I tried to do that but it introduced extra discouraged access warnings thus this PR. I haven't searched why everything went internal at some point thus I'm making public only the parts that lsp4e needs that I am sure should be proper API.

@akurtakov akurtakov self-assigned this May 10, 2024
akurtakov added a commit to akurtakov/lsp4e that referenced this pull request May 10, 2024
It's a major version bump which made too many things internal but that
will be rectified via
eclipse-mylyn/org.eclipse.mylyn#523
akurtakov added a commit to eclipse/lsp4e that referenced this pull request May 10, 2024
It's a major version bump which made too many things internal but that
will be rectified via
eclipse-mylyn/org.eclipse.mylyn#523
@akurtakov akurtakov merged commit 7d5ae7b into eclipse-mylyn:main May 10, 2024
3 checks passed
@ruspl-afed
Copy link
Contributor

@akurtakov don't you think this discussion in the form of a monologue was too short to promote several packages to API?

More API requires more effort from severely understaffed Mylyn team, and this is why all the Mylyn WikiText API was degraded according to #444

"Discouraged access" issues in LSP4E project or any other project is not a sufficient reason to promote anything to the API in Mylyn project.

With all my respect to your contributions @akurtakov my current plan is to revert this PR before 2024-06 M3, because this is not how API should be promoted, even if some package was an API in the previous major version.

cc: @merks

@akurtakov
Copy link
Contributor Author

I did it that way as it's actually partial revert of removal of API that has been such for years. As we obviously disagree I would prefer to hear from other committers (vote maybe?) before we come to conclusion.

@akurtakov
Copy link
Contributor Author

akurtakov commented May 10, 2024

I have created #524 and let the community decide. I do believe this is the best way to settle it down in a good way according to what majority sees as best, if you disagree please comment.

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.

None yet

2 participants