Skip to content

Conversation

@cleancodecraft
Copy link

This PR Closes Issue

closes #39
closes #43

Cangas made to the following files:

  • app.component.ts - site favicon is retrieved applied the same way as in other app versions
  • app.routes.ts - wildcard redirect added applied the same way as in other app versions

What type of PR is this? (check all applicable)

  • 🅰️ Feature
  • 🐛 Bug Fix
  • 📝 Documentation Update
  • 🎨 Style
  • 🧑‍💻 Code Refactor
  • 🔥 Performance Improvements
  • ✅ Test
  • 🤖 Build
  • 🔁 CI
  • 📦 Chore (Release)
  • ⏩ Revert

Mobile & Desktop Screenshots/Recordings

[Attach screenshots or recordings if applicable]

Steps to QA

Added to documentation?

  • 📜 README.md
  • 🙅 no documentation needed

[Optional] Post-deployment tasks

[Specify any post-deployment tasks that need to be performed]

[Optional] What gif best describes this PR or how it makes you feel?

[Embed gif or describe the feeling in plain text]

@cleancodecraft cleancodecraft self-assigned this Mar 17, 2024
@esteecodes esteecodes merged commit 9e5cc71 into HashnodeWithAngular:develop Mar 17, 2024
@cleancodecraft cleancodecraft removed their assignment Sep 1, 2025
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.

Feature: add a wildcard redirect in routes.ts for non existing routes Set a site favicon to be connected to blog owner

2 participants