Skip to content

Add comments and javadocs to match ctre code - #80

Merged
Adrianamm merged 18 commits into
frcsoftware:mainfrom
Spaceman113138:update-docstrings
Aug 30, 2026
Merged

Add comments and javadocs to match ctre code#80
Adrianamm merged 18 commits into
frcsoftware:mainfrom
Spaceman113138:update-docstrings

Conversation

@Spaceman113138

@Spaceman113138 Spaceman113138 commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Description

Adds the wpilib template comments and javadocs to the rev stage 1a code to match the ctre code. Result of this review: #51 (review)

Meta

Merge checklist:

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown

🌐 Preview URL: https://pr-80.frcsoftware.pages.dev

@samfreund samfreund left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Point of clarification, docstrings are for python, javadoc is what we'd call it for Java.

@samfreund
samfreund force-pushed the update-docstrings branch from 9627e99 to 08dd9f5 Compare July 6, 2026 04:53
@Spaceman113138
Spaceman113138 marked this pull request as ready for review July 6, 2026 04:57
@Spaceman113138
Spaceman113138 requested a review from samfreund July 6, 2026 21:40
@samfreund

Copy link
Copy Markdown
Member

Point of clarification, docstrings are for python, javadoc is what we'd call it for Java.

Address please

@Spaceman113138 Spaceman113138 changed the title Add docstrings to match ctre code Add comments and javadocs to match ctre code Jul 6, 2026
@Spaceman113138

Copy link
Copy Markdown
Contributor Author

Point of clarification, docstrings are for python, javadoc is what we'd call it for Java.

Address please

The new title should be more accurate.

@roboteer5291 roboteer5291 added REV Any starter code or curriculum material touching REV libraries Stage 1 Starter Code Code for students to build on - Java, WPILib, etc labels Jul 21, 2026
Adrianamm
Adrianamm previously approved these changes Aug 26, 2026
@Adrianamm
Adrianamm merged commit 488baad into frcsoftware:main Aug 30, 2026
8 checks passed
zachwaffle4 added a commit to ftcsoftware/ftcsoftware.org that referenced this pull request Aug 30, 2026
* Stage1a auto + additonal motors (frcsoftware#194)

## Description

Adds stage 1a curriculum for programing a simple auto as well as
progiraming the IntakeLauncher and Feeder motors. Makes progress on frcsoftware#13
.

Todo:
- [x]  Video + text on running the simple auto
- [x]  Talk about FuelSim
- [x] Update FuelSim to use `periodic()` over `update()`
- [x]  Video + text on AScope graph with additonal motors
- [x]  Video + text on Ascope 3d with additional motors

## Meta

Merge checklist:

- [x] Pull Request title is [short, imperative
summary](https://cbea.ms/git-commit/) of proposed changes
- [x] The description documents the _what_ and _why_, including events
that led to this PR
- [x] Pull Request has been [linted and
formatted](https://frcsoftware.org/contribution/styleguide/#linting-and-formatting)
and follows the
[styleguide](https://frcsoftware.org/contribution/styleguide)

---------

Co-authored-by: Adriana <16786568+Adrianamm@users.noreply.github.com>

* Stage 1B: Explain what a task is for/will accomplish (frcsoftware#183)

## Description

What changed? Why? (the code + comments should speak for itself on the
"how")

Some tasks failed to explain what they are for/what they accomplish.
This PR adds extra lines to fix that.

Draft for now as I only did a quick sweep and want other eyes to catch
more locations.

Closes frcsoftware#167.

## Meta

Merge checklist:

- [x] Pull Request title is [short, imperative
summary](https://cbea.ms/git-commit/) of proposed changes
- [x] The description documents the _what_ and _why_, including events
that led to this PR
- [x] Pull Request has been [linted and
formatted](https://frcsoftware.org/contribution/styleguide/#linting-and-formatting)
and follows the
[styleguide](https://frcsoftware.org/contribution/styleguide)

---------

Co-authored-by: Adriana <16786568+Adrianamm@users.noreply.github.com>

* Fix AstroJS deprecation warnings (frcsoftware#201)

PR frcsoftware#171 introduced a deprecated warning from the use of remarkRehype
without specifying unified() as the markdown processor.

This PR also bumps starlight-links-validator to the latest version to
resolve a second deprecation warning.

---------

Co-authored-by: Zach Harel <zach@zharel.me>

* Stage 1A: Code snippet fixed and clarified text about main (frcsoftware#191)

## Description

What changed? Why? (the code + comments should speak for itself on the
"how")
Code snippets for main.java didn't match so that was fixed. Also
reworded the part about main to make it clear that it shouldn't be
edited.


Merge checklist:

- [x] Pull Request title is [short, imperative
summary](https://cbea.ms/git-commit/) of proposed changes
- [x] The description documents the _what_ and _why_, including events
that led to this PR
- [x] Pull Request has been [linted and
formatted](https://frcsoftware.org/contribution/styleguide/#linting-and-formatting)
and follows the
[styleguide](https://frcsoftware.org/contribution/styleguide)

Co-authored-by: Zach Harel <zach@zharel.me>

* Add comments and javadocs to match ctre code (frcsoftware#80)

## Description

Adds the wpilib template comments and javadocs to the rev stage 1a code
to match the ctre code. Result of this review:
frcsoftware#51 (review)

## Meta

Merge checklist:

- [x] Pull Request title is [short, imperative
summary](https://cbea.ms/git-commit/) of proposed changes
- [x] The description documents the _what_ and _why_, including events
that led to this PR
- [x] Pull Request has been [linted and
formatted](https://frcsoftware.org/contribution/styleguide/#linting-and-formatting)
and follows the
[styleguide](https://frcsoftware.org/contribution/styleguide)

---------

Co-authored-by: Adriana <16786568+Adrianamm@users.noreply.github.com>

* Minor clean ups in sidebar and course overview (frcsoftware#208)

## Description
What changed? Why? (the code + comments should speak for itself on the
"how")
For Stage 0, Stage 1, Stage 1, Stage 1A and Stage 1B, the sidebar used
the word "Introduction" for the overview. However, the overview page had
a header which said "Stage # Overview". I adjusted it so instead of
"Stage # Introduction" it is now "Stage # Overview". It's more
consistent

The Course overview got small updates, including:
- The list for Stage 0 was out of date. That was updated to reflect what
is currently in the stage 0 sidebar
- It was "Stage1A" "Stage1B" but I added a space to keep it consistent.
it's now "Stage 1A" and "Stage 1B"
- The sentence for describing 1B was updated to better reflect what it
is. also the flow of the setence didn't quite make sense before. `Add
Command-Based programming, a file structure for programming FRC robots,
to kitbot` vs `Learn Command-Based programming, a file structure for
programming FRC robots, by adding it to code written in 1A.`
- The link to Stage1 now directs to Stage1 overview. Before it did not

## Meta

Merge checklist:

- [x] Pull Request title is [short, imperative
summary](https://cbea.ms/git-commit/) of proposed changes
- [x] The description documents the _what_ and _why_, including events
that led to this PR
- [x] Pull Request has been [linted and
formatted](https://frcsoftware.org/contribution/styleguide/#linting-and-formatting)
and follows the
[styleguide](https://frcsoftware.org/contribution/styleguide)

---------

Co-authored-by: Zach Harel <zach@zharel.me>

---------

Co-authored-by: Spaceman 11 <135277197+Spaceman113138@users.noreply.github.com>
Co-authored-by: Adriana <16786568+Adrianamm@users.noreply.github.com>
Co-authored-by: ハイドラ <thecomputer314@gmail.com>
Co-authored-by: httphypixelnet <91695346+httphypixelnet@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

examples REV Any starter code or curriculum material touching REV libraries Stage 1 stage1 Starter Code Code for students to build on - Java, WPILib, etc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants