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.

Sign up for GitHub

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

Jump to bottom

Add "main.h" file not found to FAQ #128

Closed
seendsouza opened this issue May 21, 2019 · 3 comments
Closed

Add "main.h" file not found to FAQ #128

seendsouza opened this issue May 21, 2019 · 3 comments

Comments

@seendsouza
Copy link
Contributor

As @theol0403 mentioned on Discord, this issue seems to pop up a lot nowadays, so I'll add it to a FAQ if wanted. I'm not exactly sure where to put it though. The General Use FAQ is a bit general, the Coding FAQ that consists of run-time and compile-time issues don't categorize this issue (linter and compile_commands.json), and there's also the PROS FAQ.
@theol0403
Copy link

The error of "main.h" not found is caused by invalid linter cache, and that is the first problem it encounters (as main.h is usually at the top of the file).
I wrote an explanation on VexForum, but it will have to be reworded for the docs.
We need to figure where to put it, and to what depth to explain.

@HotelCalifornia
Copy link
Contributor

As far as where to put it, I think it could go on the coding FAQ page either in a new section or just above the other two sections

@seendsouza seendsouza mentioned this issue Jun 8, 2019
Merged
HotelCalifornia added a commit that referenced this issue Sep 3, 2019
@seendsouza @HotelCalifornia
Add "main.h" file not found to Coding FAQ (#129)
4a4d20a 
* Add "main.h" file not found to Coding FAQ

Closes issue #128.

* Fix formatting issue with "main.h" file not found

* Fix description of main.h not found error

Account for error during project creation
Refactor case where there are hidden errors

* Fix misplaced word and improve wording

Closes issue #128

* Apply suggestions from code review

Closes issue #128

Co-Authored-By: Alex Brooke <akb.sbc@gmail.com>
@nathan-moore
Copy link
Member

This was fixed by #129

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@HotelCalifornia @theol0403 @nathan-moore @seendsouza