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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Customizable Card Title & Content #7

Closed
wants to merge 6 commits into from
Closed

Conversation

mkwsra
Copy link

@mkwsra mkwsra commented Jan 7, 2024

You can feel free to not merge this PL, this is what I did:

  • Added cover photo to ReadMe
  • Changed Record Title Attribute to cardTitle with getCardTitle() function
  • Added cardContent with getCardContent() function
  • Minor changes to ReadMe

Thanks for this Plugin ya bro.

BTW @waelkhalifa and I were parallel-programming these changes to have some excited hours 馃檶 Thanks to you Mo

@mkwsra mkwsra mentioned this pull request Jan 7, 2024
@mokhosh
Copy link
Owner

mokhosh commented Jan 8, 2024

Salaam @mkwsra and thank you for putting the time and thought into this PR.

It is currently possible to customise the card title and content, however, the concerns of data layer and presentation layer are separated.
You can override the transformRecords method to pass as much data as you need to your view. And you can publish the views and add as much html, css, and php code as you need for your card.

Anything more than a title and a status shouldn't be absolutely necessary for the most basic form of a Kanban Board.

You can see a visual example of how it's being customised with the current architecture, in the OP of this PR:
#3

Here are a few suggestions I have for your future PRs:

  1. Never open a PR from your main branch. Always create a feature branch. Otherwise you can't open another PR until the first one is merged, and even when it is merged you cannot pull from upstream because your main brach will have conflicts.
  2. Open separate PRs for separate issues. For example you have made some good changes to the README here, that I would be more open to merging, if they weren't bundled with unrelated commits.
  3. Try to match the style of the codebase as closely as possible. As you can see I'm avoiding PHPDoc comments, and using native php types. Also I'm never using mixed as a type.

Let me know if you want to make a separate PR just for the docs, or I should go ahead and add clarifications myself.

Thank you again for your PR.

@mokhosh mokhosh closed this Jan 8, 2024
@mkwsra
Copy link
Author

mkwsra commented Jan 8, 2024

Salams,

Thanks for your message, and sounds good I will see what I can do, and all thanks are to you for doing this plugin.

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

Successfully merging this pull request may close these issues.

None yet

2 participants