Skip to content

Conversation

@leagrdv
Copy link
Contributor

@leagrdv leagrdv commented Dec 11, 2025

📄 Description

Datepicker functionality implementation

The CSS is temporary and is not 100% accurate to what is expected. It was mainly copied from Myrta's test PR. The actual styling of the calendar will be done in #6304

🚀 Demo

https://preview-6843--swisspost-design-system-next.netlify.app/?path=/docs/eb77cd02-48b2-42e1-a3e4-cd8a973d431e--docs&devModeEnabled=true


🔮 Design review

  • Design review done
  • No design review needed

📝 Checklist

  • ✅ My code follows the style guidelines of this project
  • 🛠️ I have performed a self-review of my own code
  • 📄 I have made corresponding changes to the documentation
  • ⚠️ My changes generate no new warnings or errors
  • 🧪 I have added tests that prove my fix is effective or that my feature works
  • ✔️ New and existing unit tests pass locally with my changes

@leagrdv leagrdv linked an issue Dec 11, 2025 that may be closed by this pull request
5 tasks
@changeset-bot
Copy link

changeset-bot bot commented Dec 11, 2025

⚠️ No Changeset found

Latest commit: 40be72c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@swisspost-bot
Copy link
Contributor

swisspost-bot commented Dec 11, 2025

Related Previews

@leagrdv leagrdv marked this pull request as ready for review December 12, 2025 14:29
@leagrdv leagrdv requested a review from a team as a code owner December 12, 2025 14:29
@oliverschuerch
Copy link
Contributor

@leagrdv and @myrta2302
Since this is a very big and complex component, I would like to have another reviewer involved, if this is ok?

@alizedebray alizedebray removed their request for review January 8, 2026 07:56
@socket-security
Copy link

socket-security bot commented Jan 8, 2026

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm entities is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: pnpm-lock.yamlnpm/entities@4.5.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm safer-buffer is 94.0% likely obfuscated

Confidence: 0.94

Location: Package overview

From: pnpm-lock.yamlnpm/@angular/cli@19.2.19npm/safer-buffer@2.1.2

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@socket-security
Copy link

socket-security bot commented Jan 12, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addeddomhandler@​5.0.31001009880100
Addedrollup-plugin-visualizer@​5.12.09910010083100
Addedreact@​18.3.11001008497100
Addednode-fetch@​2.7.09910010085100
Addedtslib@​2.8.110010010085100
Addedtypescript@​5.8.31001009010090
Addedreact-dom@​18.3.11001009298100

View full report

@leagrdv
Copy link
Contributor Author

leagrdv commented Feb 5, 2026

@alionazherdetska I've assigned this review to you as Oli won't be able to do it. Note that the design of the datepicker isn't the same as on Figma, this will be handled in another PR done by Myrta

@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 5, 2026

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.

[web component func] Datepicker

5 participants