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 flutter version 3.27 compatible #71

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Johnny-Luu
Copy link

adjust to adapt new flutter version 3.27

@Johnny-Luu Johnny-Luu changed the title fix new flutter version error fix flutter version 3.27 compatible Dec 16, 2024
@paulpjoby
Copy link

@Johnny-Luu , Hopefully this fix should solve the build issue I'm facing when using latest Xcode cloud to build the iOS app ?

Users/local/.pub-cache/hosted/pub.dev/timelines-0.1.0/lib/src/connector_theme.dart:86:12: Error: The method 'hashValues' isn't defined for the class 'ConnectorThemeData'.

@Johnny-Luu
Copy link
Author

@Johnny-Luu , Hopefully this fix should solve the build issue I'm facing when using latest Xcode cloud to build the iOS app ?

Users/local/.pub-cache/hosted/pub.dev/timelines-0.1.0/lib/src/connector_theme.dart:86:12: Error: The method 'hashValues' isn't defined for the class 'ConnectorThemeData'.

yes, it should be possible to fix that issue
while this PR hasn't been merged, you can make a hotfix by cloning this repo and apply these changes, then temporarily use that repo in your project

@paulpjoby
Copy link

@Johnny-Luu , Hopefully this fix should solve the build issue I'm facing when using latest Xcode cloud to build the iOS app ?
Users/local/.pub-cache/hosted/pub.dev/timelines-0.1.0/lib/src/connector_theme.dart:86:12: Error: The method 'hashValues' isn't defined for the class 'ConnectorThemeData'.

yes, it should be possible to fix that issue while this PR hasn't been merged, you can make a hotfix by cloning this repo and apply these changes, then temporarily use that repo in your project

Never did a hotfix before. So forgive me if I sound stupid. So I would be forking this repo and then applying this changes and using my custom repo instead of using the timeline being mentioned in the pub spec yaml, is it correct ?

@Johnny-Luu
Copy link
Author

Johnny-Luu commented Dec 27, 2024

Never did a hotfix before. So forgive me if I sound stupid. So I would be forking this repo and then applying this changes and using my custom repo instead of using the timeline being mentioned in the pub spec yaml, is it correct ?

correctly bro, in your pubspec.yaml will look like this:
before:
timelines: ^0.1.0
after:

  timelines:
    git:
      url: https://github.com/<your-user>/timelines
      tag: main

@paulpjoby
Copy link

Never did a hotfix before. So forgive me if I sound stupid. So I would be forking this repo and then applying this changes and using my custom repo instead of using the timeline being mentioned in the pub spec yaml, is it correct ?

correctly bro, in your pubspec.yaml will look like this: before: timelines: ^0.1.0 after:

  timelines:
    git:
      url: https://github.com/<your-user>/timelines
      tag: main

That's beautiful. Awesome bro !!! ❤️ I never knew that before. Thanks a ton !!!!

@lsh411
Copy link

lsh411 commented Jan 3, 2025

Thank you

Never did a hotfix before. So forgive me if I sound stupid. So I would be forking this repo and then applying this changes and using my custom repo instead of using the timeline being mentioned in the pub spec yaml, is it correct ?

correctly bro, in your pubspec.yaml will look like this: before: timelines: ^0.1.0 after:

  timelines:
    git:
      url: https://github.com/<your-user>/timelines
      tag: main

Thank you very much !!!

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.

5 participants