ladyjaye
ladyjaye
This would be great! Really appreciate looking into it!
I ran into this as well. I ended up with a jest config like this to work around it: ```javascript const { defaults: tsjPreset } = require("ts-jest/presets"); module.exports = {...
Ah, I didn't consider the multiple shells entering the folder problem, aka using something like tmux would present this problem. I often run my unit tests from another shell session/pane...
I just ran into this and have screenshots =) When I have the following in my `settings.json` ```json { // "jest.autoRun": "off" } ``` The code lens display shows "Debug(4)"...
How do you deny it? Just raise an exception? ``` raise Exception("something bad happened") ``` And for it to succeed you just return the `event`? ``` return event ```
I want to also confirm that if the user created an account, but the account is unconfirmed, it throws a UserNotFoundException. Is there no way to get the unconfirmed user...
Is anyone opposed to setuptools entry points for handling this? I'm going to assume the most natural place to something like this is for users to write their own Jinja2...
See Pull Request #103
@aleksandrmelnyk did you have success with this?
I ran into this too... there's a few places where it's relevant in the source: https://github.com/igorescobar/jQuery-Mask-Plugin/blob/master/src/jquery.mask.js#L389 This sets the first `oldValue`, if the initial value of your input is ""...