[API design] Remove "AI" prefix everywhere #329
Replies: 5 comments 5 replies
-
|
@devcrocod @EugeneTheDev could you please take a look at @ptitjes suggestions and share your thoughts? Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
In some of our earlier discussions we touched on this topic, and there was a good point mentioned: |
Beta Was this translation helpful? Give feedback.
-
|
I agree with @EugeneTheDev; Moreover, removing this prefix would be a breaking change and cause a lot of merge conflicts (because there are a lot of concurrent PRs) |
Beta Was this translation helpful? Give feedback.
-
|
I understand @EugeneTheDev 's argument though I only agree with it to a certain extent. Because this leads to extra long interfaces and class names. This is exacerbated by a lot of the concepts being duplicated, often uselessly, with a class and a This is similar to for the method names choices. There are so many methods with really close names but one or more different words, all of them defined publicly, also with consistency problems. Because of that, the API is currently very difficult to discover, understand and use, with too many public APIs. Even these days, a lot of PRs are merged with a bunch of new public symbols, when these mostly should be made internal. A lot of these problems come from the fact that Finally, I'd like to add that a lot of these design/naming choices go against JetBrains' own guidelines for library authors... |
Beta Was this translation helpful? Give feedback.
-
|
@ptitjes I mostly agree with your points here, and I have similar concerns. Unfortunately, given the current (quite rapid) pace of development and the scope we want to cover, it is problematic to address these issues. A lot of new functionality is being added, refactored, or changed, which is to be expected at this stage of framework development. We definitely need to address this before the first stable release though, that's true. But if you have any suggestions on how we can improve the current situation, we would be glad to hear them. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
See #215
Beta Was this translation helpful? Give feedback.
All reactions