Converge to one coding style for datatypes #135
Labels
No labels
Component: User interface
Component: Wymeditor
Help wanted
Level: Difficult
Level: Easy
Level: Moderate
Pagetype: Festival
Pagetype: Mailinglist
Pagetype: Peer reviewed article
Pagetype: Text
Privacy GDPR AVG
status: has conflicts
Status: Needs changes
Status: Needs discussion
Status: Needs review
Status: Ready to merge
Status: Waiting for response
Type: Bug
Type: Enhancement
Type: Question
Usecase: De Stadsbron
Usecase: Koppelting
Usecase: MeetjeStad
Value: Coders
Value: Security
Value: Users
Value: Visitors
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
harmen/hypha#135
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Various datatypes (web page, article, festival) now have different coding styles. We need to compare these and make a choice for some preferred way of implementing a new module.
Things to keep in mind:
https://github.com/PlanBCode/hypha/blob/newtext/system/datatypes/text.php is a suggestion for a new structure
This refactor is tracked in parts:
After all datatypes are completed, some additional refactoring can be done to make sure that instead of one global
<form>tag, there will be one for each form separately.After this is complete, I would also like to see #264 done and maybe #274.
Text, mailinglist and article have now been converted. Festival is in progress at #337. The settings special datatype should probably also be converted to allow #264 to be done.