User guide on wicket-11.x still says Wicket 10.x
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- java
- Domain
- documentation
Research direction
On the wicket-11.x branch, inspect single.adoc, introduction.adoc and keepControl_9.adoc; update the guide title and introduction to Wicket 11 and point the EnclosureContainer link to the 11.x module-layout apidocs. Check the same text on master and update it for Wicket 12. Done when both branches use the correct versions and API link.
Written by the indexing model from the issue text.
Description
The user guide on wicket-11.x still presents itself as the Wicket 10 guide:
single.adoctitles it "Wicket 10.x Reference Guide"introduction.adocsays "this guide is based on Wicket 10"keepControl_9.adoclinksEnclosureContainerin the 10.x apidocs
The title and introduction should name Wicket 11, and the link should point to the 11.x apidocs (which use the module layout, apidocs/11.x/org.apache.wicket.core/...).
master has the same text and should name Wicket 12 there.
- Dominant language
- Java
- Stars
- 799
- Forks
- 420
- Avg merge
- 18h 37m
- Merged PRs (30d)
- 140
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: 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 apache/wicket
-
Document and enforce pull request review guidelinesPossibly taken @dashorst claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
COOP and COEP exemptions compare with the context path, so page exemptions never matchPossibly taken @asvanberg claimed this 18 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
apache/wicket#1661 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
The CSP report-uri is lost in development mode because strict() clears itMay be free again @VelpulaGangavardhan claimed this 23 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/wicket#1660 · 5 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
`Time.at(t, in: nil)` returns UTC instead of the local time (or the time zone of `t`), unlike CRubyOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
hermes-queue
Difficulty 1/5 Under an hour Newbie friendliness 72/100
chrisalunlloyd2-sudo/mindpalace#349 ·
Maintainers usually reply within 1 day
-
Retry-After parser accepts invalid delay-seconds valuesPossibly taken @Dhruvraj-Rana claimed this today. OpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
open-telemetry/opentelemetry-java#9018 ·
Maintainers usually reply within 2 days
-
bug priority: medium Review effort [1-5]: 2 status: needs-triage type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
carlos-emr/carlos#5818 ·
Maintainers usually reply within 1 day
-
bug good first issue help wanted tooling
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
appmonster007/kmip-adapter#100 ·