-
Notifications
You must be signed in to change notification settings - Fork 150
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
responsive_utils.dart not included as an export in responsive_framework.dart #181
Comments
Let's add it ASAP.
That's a serious issue. Can you open a PR and I'll add you as a contributor
too.
…On Fri, 21 Jun 2024, 12:18 am Mike Stainer, ***@***.***> wrote:
@rayliverified <https://github.com/rayliverified>
—
Reply to this email directly, view it on GitHub
<#181 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEXZO3QB6W7E4BVMHEOQ4KTZIOZQXAVCNFSM6AAAAABJVFYBVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBSGAYTONBTGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@rayliverified Any prevision on when this gets published? |
Not yet. I need to bundle some other changes for publishing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When developing for web, the
breakpointsLandscape
property ofResponsiveBreakpoints.builder
does not work as intended because the default value of_landscapePlatforms
inresponsive_breakpoints.dart
is set to the following:In order to overcome this we need to set the
landscapePlatforms
property ofResponsiveBreakpoints.builder
. However, because responsive_utils.dart is not included as an export in the barrel file, we cannot access theResponsiveTargetPlatform
class directly but have to manually import the fileimport 'package:responsive_framework/src/utils/responsive_utils.dart';
which gives us the following error.Is it possible to add the
responsive_utils.dart
to the export file or move to a new location that is accessible through the import?Many thanks
The text was updated successfully, but these errors were encountered: