Issue #1125: Allow markdown formatting in "Description"

[kuchtiak-ufal]

Now,

Based on the

MarkdownConfig = {
    enabled: false,
    mathjax: false,
  };

definition user can use the https://commonmark.org/ or for https://www.mathjax.org/ formatting in the description property.

Example:
Description Metadata text:

## Math Expression
___
* enabled: true
* mathjax: true
___
The [Demo](https://www.mathjax.org/#demo)

When $a \ne 0$, there are two solutions to $ax^2 + bx + c = 0$ and they are
$$x = {-b \pm \sqrt{b^2-4ac} \over 2a}.$$

Result:

[Copilot]

Pull Request Overview

This PR implements markdown formatting support for description metadata fields in DSpace items. Users can now enable markdown and MathJax formatting in description fields through configuration.

Key changes:

• Added configuration injection to access markdown settings
• Implemented conditional rendering between plain text and markdown formats
• Fixed trailing comma syntax error in configuration

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/config/default-app-config.ts	Fixed trailing comma syntax error in markdown configuration
src/app/item-page/simple/field-components/clarin-description-item-field/clarin-description-item-field.component.ts	Added configuration injection and conditional logic for markdown rendering
src/app/item-page/simple/field-components/clarin-description-item-field/clarin-description-item-field.component.html	Added conditional rendering with markdown pipe when enabled

[Copilot]

Pull request overview

Copilot reviewed 27 out of 27 changed files in this pull request and generated 7 comments.

Comments suppressed due to low confidence (1)

src/app/submission/sections/cc-license/submission-section-cc-licenses.component.spec.ts:267

• These specs now use real timers (setTimeout + done) to wait for debounced behavior. This makes the suite slower and more flaky compared to the existing fakeAsync/tick pattern already used in this file. Prefer wrapping these tests in fakeAsync and advancing time with tick(...) (or flushing the debounce scheduler) instead of using real timeouts.

      it('should call the submission cc licenses data service getCcLicenseLink method', (done) => {
        setTimeout(() => {
          fixture.detectChanges();
          expect(submissionCcLicenseUrlDataService.getCcLicenseLink).toHaveBeenCalledWith(
            ccLicence,
            new Map([
              [ccLicence.fields[0], ccLicence.fields[0].enums[1]],
              [ccLicence.fields[1], ccLicence.fields[1].enums[0]],
            ])
          );
          done();
        }, 350);
      });

      it('should display a cc license link', (done) => {
        // Wait for the debounced observable to emit
        setTimeout(() => {
          fixture.detectChanges();
          const linkElement = de.query(By.css('.license-link'));
          expect(linkElement).toBeTruthy();
          done();
        }, 350); // Wait longer than the 300ms debounce
      });

[Copilot]

This update enables markdown + MathJax by default in the main runtime config. That’s a significant behavior and performance change (MathJax rendering can be expensive, and enabling markdown affects how user-provided metadata is displayed). Please confirm this is intentional for all deployments; otherwise keep defaults disabled and document/enable per environment as needed.

Suggested change

	markdown:
	enabled: true
	mathjax: true
	# Markdown rendering configuration.
	# Disabled by default for performance and to avoid changing how user-provided metadata is displayed.
	# Enable these options in an environment-specific config only if your deployment requires them.
	markdown:
	enabled: false
	mathjax: false

[amadulhaxxani]

@kosarko
seems like that’s a product decision