You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stuck in my PHP mindset when starting this project, I separated functionality of many views in two pieces: one view to display the data stored in the database, and another to make changes to the data.
Example:
dj3/forms/new_sub_request/$ (submission form for users to create a new request)
passes data via POST to
dj3/forms/process_sub_request/
and process_sub_request validates the input writes the new SubRequest object to the database.
However, after reading more, it seems to make more sense to just concat these two views into one, and switch between modes via GET variables ($process=1). At least, this is what I see most other projects doing.
The text was updated successfully, but these errors were encountered:
Stuck in my PHP mindset when starting this project, I separated functionality of many views in two pieces: one view to display the data stored in the database, and another to make changes to the data.
Example:
dj3/forms/new_sub_request/$ (submission form for users to create a new request)
passes data via POST to
dj3/forms/process_sub_request/
and process_sub_request validates the input writes the new SubRequest object to the database.
However, after reading more, it seems to make more sense to just concat these two views into one, and switch between modes via GET variables ($process=1). At least, this is what I see most other projects doing.
The text was updated successfully, but these errors were encountered: