C++ Project Import Warning
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Reproduce the import by bringing a 2025 or 2026 C++ project into 2027 alpha-7 and selecting Import Project. Trace the importer from the warning about determining the robot class, then check how it updates includes and namespaces. Done means the project imports without requiring manual robot-class input and the relevant includes and namespaces are fully updated.
Written by the indexing model from the issue text.
Description
When importing a 2025 or 2026 project into 2027 alpha-7 in c++, after clicking Import Project, I get the following warning : Failed to determine robot class. Enter it manually? with the option to enter respond yes or no.
After clicking yes, the project seems to correctly be imported although with a lot of the includes and namespaces changes not being fully changed automatically
- Dominant language
- Java
- Stars
- 186
- Forks
- 24
- Avg merge
- 8h 27m
- Merged PRs (30d)
- 9
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wpilibsuite/SystemcoreTesting
-
Limelight Pending
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
wpilibsuite/SystemcoreTesting#383 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
wpilibsuite/SystemcoreTesting#380 ·
-
Limelight Pending
Difficulty 1/5 Under an hour Newbie friendliness 78/100
wpilibsuite/SystemcoreTesting#315 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
wpilibsuite/SystemcoreTesting#392 ·
-
Limelight
Difficulty 3/5 1-2 days Newbie friendliness 57/100
wpilibsuite/SystemcoreTesting#389 · 1 comment ·
All issues in wpilibsuite/SystemcoreTesting
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nextcloud/notes-android#3367 ·
Maintainers usually reply within 1 day
-
Feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MuntashirAkon/AppManager#2058 ·
-
SarifLogger: artifactLocation.uri is not properly encoded for file names containing '#', '?', or '%'Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
checkstyle/checkstyle#21721 ·
Maintainers usually reply within 1 day