Feature #20838

as a developer I would like to create new forms using react/redux

Added by Ohad Levy 9 months ago. Updated 7 months ago.

Status:Closed
Priority:Normal
Assigned To:Ohad Levy
Category:JavaScript stack
Target version:Team UX - Iteration 22
Difficulty: Bugzilla link:
Found in release: Pull request:https://github.com/theforeman/foreman/pull/4795
Story points-
Velocity based estimate-
Release1.17.0Release relationshipAuto

Description

this should enable the infrastructure for a developer to write a new form using react and redux.

this should include
  • form fields (input, text, checkbox, textarea etc)
  • client side form validations
  • API handling for submitting the form
  • server side validation errors.

This should also mimic the current workflow in foreman, e.g. success toast after a 'resource' is being created.


Related issues

Related to Foreman - Feature #20839: implement bookmark creation using react Closed 09/04/2017
Related to Foreman - Feature #21134: Get i18n working for validators in react forms Assigned 09/27/2017

Associated revisions

Revision b0fd1ab6
Added by Ohad Levy 7 months ago

fixes #20838 - add redux-form supports

History

#1 Updated by Ohad Levy 9 months ago

  • Related to Feature #20839: implement bookmark creation using react added

#2 Updated by The Foreman Bot 9 months ago

  • Status changed from New to Ready For Testing
  • Assigned To set to Ohad Levy
  • Pull request https://github.com/theforeman/foreman/pull/4795 added

#3 Updated by Daniel Lobato Garcia 9 months ago

What should be implemented for this issue to be closed? What parts of the stack is this substituting, just the view (which would include client-side validations) or does this imply more than that?

#4 Updated by Walden Raines 8 months ago

  • Target version set to Team UX - Iteration 21

#5 Updated by Ohad Levy 8 months ago

  • Related to Feature #21134: Get i18n working for validators in react forms added

#6 Updated by Ohad Levy 8 months ago

Daniel Lobato Garcia wrote:

What should be implemented for this issue to be closed? What parts of the stack is this substituting, just the view (which would include client-side validations) or does this imply more than that?

Daniel - Does the PR address your question?

#7 Updated by Walden Raines 7 months ago

  • Target version changed from Team UX - Iteration 21 to Team UX - Iteration 22

#8 Updated by Timo Goebel 7 months ago

  • Release set to 1.17.0

#9 Updated by Ohad Levy 7 months ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF