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

2437 Correct and clarify commented-out code in several custom components #2438

Merged

Conversation

hardyoyo
Copy link
Member

@hardyoyo hardyoyo commented Aug 15, 2023

References

Description

  • Correct the path in commented-out code in the custom theme's
    components
  • Clarify that the workflow-item-send-back.component.scss file is a stub (it has no corresponding SCSS file in the base theme)

Instructions for Reviewers

n/a

List of changes in this PR:
(see description)

Include guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes.

Issue #2437 contains a description of how to reproduce. With this patch applied, confirm the bug is no longer present, and that the footer is easily customizable.

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

  • My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
  • My PR passes ESLint validation using yarn lint
  • My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
  • [na] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
  • My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
  • [na] If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
  • [na] If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
  • If my PR fixes an issue ticket, I've linked them together.

- Correct the path in commented-out code in the custom theme's
  components
- Clarify that the workflow-item-sen-back.component.scss file is a stub
- It has no corresponding SCSS file in the base theme
@tdonohue tdonohue added bug code task themes 1 APPROVAL pull request only requires a single approval to merge port to dspace-7_x This PR needs to be ported to `dspace-7_x` branch for next bug-fix release labels Aug 16, 2023
@tdonohue tdonohue added this to the 7.6.1 milestone Aug 16, 2023
Copy link
Member

@tdonohue tdonohue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Thanks @hardyoyo ! This is very obviously correct & only updates comments (no actual code changes). But you are correct, these paths should all start with ./ in the "custom" theme to ensure the file in the current directory is used.

@tdonohue tdonohue merged commit fbb04a0 into DSpace:main Aug 23, 2023
10 checks passed
@dspace-bot
Copy link
Contributor

Successfully created backport PR for dspace-7_x:

@tdonohue tdonohue modified the milestones: 7.6.1, 8.0 Aug 23, 2023
@tdonohue tdonohue removed the port to dspace-7_x This PR needs to be ported to `dspace-7_x` branch for next bug-fix release label Aug 23, 2023
4science-it pushed a commit to 4Science/dspace-angular that referenced this pull request Oct 25, 2024
…request DSpace#2438)

[DSC-1864] fix template function

Approved-by: Giuseppe Digilio
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 APPROVAL pull request only requires a single approval to merge bug code task themes
Projects
No open projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

Bug: Custom theme contains incorrect commented-out code, like a trap
3 participants