Giter VIP home page Giter VIP logo

Comments (6)

tmenier avatar tmenier commented on August 29, 2024 1

Your options seem clear: upgrade just Flurl and take your chances, or don't until you're ready to upgrade both. I recommend the latter. I don't see any practical value in what you requested.

from flurl.

tmenier avatar tmenier commented on August 29, 2024

What's the motivation for updating just Flurl and not Flurl.Http?

from flurl.

springy76 avatar springy76 commented on August 29, 2024

I wan't to reduce the amount of "old" packages as much as possible. While I also would like to update Flurl.Http this step will require a huge amount of time (I currently don't have) for changes and thorough testing due to the many breaking changes - not speaking of getting rid of Newtonsoft.Json which will require even more work (for all the data models, might be easier with STJ 8.0 now) but can be postponed using the migration package, but this also has to be initialized for all dependent projects, so Flurl.Http 3.x will be used more longer than I wish to.

from flurl.

tmenier avatar tmenier commented on August 29, 2024

If you really want to upgrade just Flurl, try it and see if anything breaks. I don't see any compelling reason to do it until you're ready to upgrade both though. They're meant to go hand in hand, so I don't plan on supporting this in any official capacity or doing further enhancements to 3.x. I just don't see a good enough reason for me to spend time on that. Sorry.

from flurl.

tmenier avatar tmenier commented on August 29, 2024

Side note: did you read the upgrade guide? There's a Newtonsoft companion lib to ease that part of the upgrade.

from flurl.

springy76 avatar springy76 commented on August 29, 2024

The upgrade guide is why I know the transition to v4 will take a huge amount of time. With "migration package" I meant the "Newtonsoft companion lib" because getting away from Newtonsoft is another big deal, alone due to the fact STJ ignores DataMemberAttributes.

I can update Flurl alone to 4x and it seems as it works well - but a MethodNotFoundException might occur at any place at any time. NuGet (transitive) dependency hell is no better than DLL hell, ex: https://stackoverflow.com/questions/77098132/error-generating-jwt-token-during-asp-net-core-web-api-authorization/77133355#comment136008891_77133355

from flurl.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.