Add a dedicated rate-limiting command for the FilePage
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
To mirror the rate-limiting commands we already have for the 2 other "workhorse" pages, CheckRateLimitForCollectionPageCommand.java and CheckRateLimitForDatasetPageCommand.java
Contributor guide
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.
Research direction
Start by reading CheckRateLimitForCollectionPageCommand.java and CheckRateLimitForDatasetPageCommand.java to understand the existing rate-limiting command pattern. Locate the FilePage command entry point and add the corresponding dedicated command, matching the behavior of the two named commands. Done means FilePage has its own rate-limiting command consistent with those existing commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100