Giter VIP home page Giter VIP logo

Comments (8)

cibernox avatar cibernox commented on August 15, 2024

Any feedback on this?

from pretender.

trek avatar trek commented on August 15, 2024

Still haven't looked. You could speed up the process by providing more details about the pros/cons of this change.

from pretender.

cibernox avatar cibernox commented on August 15, 2024

FakeXMLHttpRequest now can send onprogress events. According to the XHR spec, on progress events are triggered each 50ms during downloads and uploads

Usually you don't care about progress event, but sometimes I do. I was thinking in check if the request object has an onprogress event handler attached. If it does means that the user cares about them, and therefore I pretender should fire them regularly.

p.e. in a request with 200ms of delay the event, it would be fired each 50ms. Never before the loadStart and never after the load event.

from pretender.

cibernox avatar cibernox commented on August 15, 2024

Sorry for the insistence, but I'm just waiting some green light to start implementing something.

from pretender.

trek avatar trek commented on August 15, 2024

I'd still like to hear the pros/cons. I think you've accurately described the situation, but haven't touched on how it might affect people using the library's current behavior.

from pretender.

cibernox avatar cibernox commented on August 15, 2024

I don't think that there is any cons. It's a new feature that should't affect in any form to current users.

The options are
a) Fire the events only if there is a listener for them.
b) Fire the events always.

Intuitively I think that option b) might be simpler to implement and triggering events is cheap enough to not be a concerned about wasting cycles. But in any case it's an implementation detail, the final result for the developer listening for progress events will be identical.

from pretender.

trek avatar trek commented on August 15, 2024

How do you feel about pretender triggering that event each 50ms by default?

Wouldn't we keep triggering events every 50ms, even after a test has finished running, whether you were using them or not? That seems like a high likelihood of ending up with test leaks?

from pretender.

cibernox avatar cibernox commented on August 15, 2024

@trek see #73 for the implementation details. The change is fairly minimal and I don't see any posibility of leaking since the next progress event is scheduled only if the request is still ongoing.

from pretender.

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.