Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merging Ampersand 4 into Ampersand 5 #1482

Open
4 tasks
stefjoosten opened this issue May 9, 2024 · 0 comments
Open
4 tasks

Merging Ampersand 4 into Ampersand 5 #1482

stefjoosten opened this issue May 9, 2024 · 0 comments
Assignees

Comments

@stefjoosten
Copy link
Contributor

stefjoosten commented May 9, 2024

The transition to Ampersand 5 is taking longer than expected. This causes worries, which we preserve in the following list. This list is a checklist with some reminders, which we intend to use when we move to Ampersand 5.

  • the Haskell function objnm, which is part of the definition of ObjectDef in Ampersand 4, must be removed and may not return into Ampersand 5 because it is of no consequence.
  • change the type identifier BoxHeader into HTMLtemplateCall throughout the Ampersand 5 source code after merging, to make the code more self-explaining for future readers.
  • Remove data BoxTxt from the Haskell source code (in AbstractSyntaxTree.hs) and integrate its contents into BoxItem, to improve code conciseness by saving one Haskell data type.
  • The field explUserdefd in data Purpose seems to have no purpose. Investigate and remove for the sake of maintainability.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants