Closed RokeJulianLockhart closed 9 months ago
These are very separate features in each app, so I'd rather prefer them raised in each of the apps. However, I have some remarks:
Notes
field, but it's a one-line input. That's why it would rather require a whole feature request to even change the single-line field to multi-line.In Notes, there's already a feature request for that, but raised wrongly: https://github.com/FossifyOrg/Notes/issues/2. If you'd like, you can raise it once again, and I'll close the old one).
https://github.com/FossifyOrg/General-Discussion/issues/126#issuecomment-1954617215
@Aga-C,
Calendars rather use HTML than Markdown and there is already a feature request for that: https://github.com/FossifyOrg/Calendar/issues/12.
That's not sufficient, because the entire raison d’être for Markdown is that it's legible as plain text, hence why HTML is frequently necessary to supplement it — its purview is narrow, but it's incredibly powerful despite it.
Why would you need markdown support in Contacts? I know we have a Notes field, but it's a one-line input. That's why it would rather require a whole feature request to even change the single-line field to multi-line.
Whether it's single-line or multiline isn't of significance to me, because I can still write as much in it as if it were multiline, there merely won't be paragraph breaks. However, how do you handle multiline note content served externally, if that's so? I do hope that an FR exists to make it multiline. If not, I'll create one.
I use my contacts like a CRM somewhat, in that I just put more information in there than most people do. It's a necessity of my employment, hence the need for at least basic formatting.
In Notes, there's already a feature request for that, but raised wrongly: https://github.com/FossifyOrg/Notes/issues/2. If you'd like, you can raise it once again, and I'll close the old one.
I'll do so.
Could you copy those explanations to your feature requests, so it'll be more visible than just link here? Thanks!
https://github.com/FossifyOrg/General-Discussion/issues/126#issuecomment-1954649955
@Aga-C, as in, you'd like me to add a link to https://github.com/FossifyOrg/General-Discussion/issues/126#issuecomment-1954631456 in the 3 referenced issues' additional information sections?
Just copy and paste those explanations.
@RokeJulianLockhart I thought you would just copy to Additional information
comments regarding each app instead of link to this. We don't need explanation e.g. in Contacts why Markdown is needed in Calendar. Please just remove these comments and copy-paste proper things to request, not as a comment.
https://github.com/FossifyOrg/General-Discussion/issues/126#issuecomment-1954802844
Done, @Aga-C. It did seem like a strange request. See https://github.com/FossifyOrg/Calendar/issues/160#issue-2144836594 and https://github.com/FossifyOrg/Contacts/issues/86#issue-2144836764. (https://github.com/orgs/community/discussions/109367#discussion-6245605)
Checklist
Which apps should have this feature?
Calendar, Contacts, Notes
Feature description
Render Markdown in Contact notes, calendar descriptions, and FOSSify Notes. Ideally, choose a Markdown processor which supports basic HTML tags like
<blockQuote>
and<details>
.Why do you want this feature?
Because I want plain-text formatting to be available to the masses, and more importantly, me.
Additional information
A great many ready-to-use FOSS Markdown processors exist.