Is Fleet even intended for compiled languages?

I'm in the same boat, searching for “error:” in the console output to refactor Swift…

Imagine telling this to a JetBrains engineer 10 years ago…

And surely they're developing Fleet using Fleet. But perhaps they're writing it in Javascript…

Olga Klisho  Please read and understand the whole original post and the underlying point. 

The issue you link to only addresses part of the problem, and even that hasn't been touched for 10 months. The Jetbrains commenter on that issue also seems to view building as a weird edge case that should be hacked in as a kind of run configuration, rather than being a first class operation.

Another indication that your product team is thinking of Fleet as an IDE mainly for interpreted languages, it would seem.

This kind of worked for me for Xcode projects only (details follow).

It's of little use without somewhere to see the errors though.

• If anyone's trying this, you have to set up a key mapping for this action (which is fine for me)
• Didn't work for for a Spring Boot project (just beeps)
• No good if you have multiple targets in your Xcode project. It kind of uses the most recent item in the run config list, but not really – if you “change” to a different config, it still builds the one that was selected before.

In general, the UI around run configurations seems a bit mad anyway. There's no way to switch configs without running a target as far as I can tell.

This is important because they're not just used for running. They seem to be the editor's idea of current build context – for symbol resolution), syntax highllighting, etc – like in the old IDEs.

It's this sort of strangeness that led me to question the intended use cases of Fleet in the first place.

Olga Klisho You are still ignoring the main point of my post though – Fleet has no way to find build errors in a project.

I explained this in the second paragraph of my original post. 

One possible solution (the “expected behaviour” you're asking for) is a Problems view which shows errors for the whole project. These exist in other Jetbrains IDEs such as IntelliJ, so I don't know why it seems so difficult to get the message across.

Here is the problem put another way:

1. Build or run the project
2. Project has compilation errors
3. Time to fix the errors, BUT: there is no practical way to know which files the errors are in. Console is useless because errors are lost amongst screeds of other output. Errors are displayed in individual files when you open them, but what are you supposed to do - open and check every single file in the project?

This is the use case. It's fundamental to the software development process – I'm not sure why I'm having to explain it again.

I suggest you show this to one of your developers. Any software developer should get what I mean instantly.

Hello,

Thank you for the details.

As I mentioned before, the issue you describe is covered by the following ticket:
https://youtrack.jetbrains.com/issue/FL-24353

The problem you’ve described is clear to me! :)

To clarify what I meant by “the issue is covered by ticket №...” in my previous comment:

• This means that the points you described in your recent and previous comments have been added to the issue with the “jetbrains-team” level of visibility.
• It also means that all these comments will be taken into account during the fix. They are treated as sub-issues, and the responsible developer is aware of all the subtasks associated with the issue.

I hope this makes everything clearer now! :)

FL-24353 is titled “Build project button”. It doesn't mention a problems view at all. If it is intended to encompass a problems view as well, it should really say so in the title or description.