-
Notifications
You must be signed in to change notification settings - Fork 364
DateString not exposed as TypeScript type - prevents use in Loopback 4 #1885
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
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@achrinza similar to my comment on another issue - if you agree that this bug is valid, perhaps it should be ignored by stalebot. |
Apologies for missing the issue; This would be solved with the addition of type definitions to Juggler. Currently we don't have the resources to implement the typedefs and tests right now but are open to community contributions. As for stalebot, it acts as a gentle reminder that the issue is still open; So if the issue is still valid, we'll remove the stale tag :) |
Currently being worked on by: #1902 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closing, as #1902 was merged |
Steps to reproduce
DateString
to a TypeScript model in loopback 4.Current Behavior
Can't import type
DateString
because it's implemented in pure JS and not exposed by any type declaration file.Expected Behavior
I'd be able to do something like
import { DateString } from "loopback-datasource-juggler"
in TypeScript code.It would appear that this is possible, as
DateString
is listed on the Loopback types page in the Loopback 4 docs.Link to reproduction sandbox
There's nothing to sandbox because the code won't even compile.
The text was updated successfully, but these errors were encountered: