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

FIX: Value could not be determined statically. #333

Merged
merged 1 commit into from
Jan 25, 2024

Conversation

Jonah-Jordan
Copy link
Contributor

@Jonah-Jordan Jonah-Jordan commented Jan 24, 2024

This commit fixes the error Value could not be determined statically when DatepickerModule is imported with .forChild() for configuration purposes.

PR Checklist

This PR fulfills the following requirements:

  • The commit message follows our guidelines: Contributing guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • A changelog entry was added

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Resolved issues

This commit fixes the error Value could not be determined statically when DatepickerModule is imported with .forChild() for configuration purposes.
@TriangleJuice TriangleJuice merged commit a294bc6 into digipolisantwerp:master Jan 25, 2024
1 check passed
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.

2 participants