3 - Climbed boulder form

[PulexIrritans]

Value statement - a requirement, not a solution

As a climber I want to enter the data for a climbed boulder in a form so that these can be used to calculate rankings and stats.

Description (Text, Scribble, Wireframe, Design)

Acceptance criteria

• [x] When the user clicks on the button "Climb" a new page is opened where the detailed BoulderCard is shown.
• [x] Below the detailed BoulderCard a form is visible where climb data can be entered for this specific boulder.
• [x] The form includes the following input fields:
• [x] Date (default selection is current date, but this can be changed)
• [x] Projected (Checkbox)
• [x] Attempts (Number)
• [x] Zone/ Top/ Flash (Radio Button)
• [x] Level Feedback - Too easy/ Just right / Too hard (Radio Button)
• [x] Like (Checkbox)
• [x] Save Button (type Submit)
• [x] None of the fields is required however at least one input must have been changed in order to enable the submit button.
• [x] The form should also have a validation so that the user can only enter the required data types.
• [x] At the bottom of the page the user can click on a link that will bring him back to the "Find" page

Tasks

• [x] Set up React router and add routes for the "Find" page and the "Add" page.
• [x] Add a link to the "Climb" button which navigates to the "Add" page.
• [x] Show the BoulderCard in Detailed view on the "Add" page.
• [x] Set up the form with the fields that are listed above.
• [x] Set up useStates in order to save and display the entered data.
• [x] Set up a useState for the Button state (enabled/ disabled)
• [x] Implement a logic to enable the button only when one of the input useStates has changed
• [x] Implement a basic link back to the "Find" page.

Size

large

[mbosselmann]

Hey Antje,

I like your user story! 👍 It is a large and you can think about making implementing the navigation as extra user story, but that is your choice. I have one remark and one question.

I will start with the question: Will you add a wireframe to your description to visualize your feature? 🤔

And my remark:

'None of the fields is required however at least one input must have been changed in order to enable the submit button. The form should also have a validation so that the user can only enter the required data types.' --> These don't have checkboxes yet. Is this intended?

[PulexIrritans]

Hi Mareike @mbosselmann , thank you for your question and your remark. I totally forgot the wireframe. This and the missing checkboxes where not intended. I would prefer to have the navigation within this user story. I think I can implement the whole thing tomorrow. However, please tell me if you as coaches prefer that I separate them. I understand that I shouldn't overload you with one pull request...

[mbosselmann]

Hi Antje, we coaches don't prefer one option. :) I just suggested to extract the navigation if you want to reduce your story, because the navigation is one component for its own with testing and storybook that could be easily separated in an own user story. But decide it for yourself. :)