Felix Ingram
Felix Ingram
This is a very interesting idea. If anyone else is looking at this issue, then I think the lines of code to look at are now these: https://github.com/spulec/moto/blob/master/moto/core/models.py#L555-L576 Looks like...
Looks like the driver string needs to be `postgres`. Note that there seems to be other issues with using postgres, as the SQL statements use backticks, which postgres does not...
One approach would be to include the expiry date in the user (e.g. `[email protected]`) and then have go-guerrilla check that and reject as needed.
This would be super useful for me. So I'm giving it a bump 😄
Not sure if this affects #46 at all. That PR had a working example of a websockets API. I can update if needed.
the parse option does seem to do most of what I want: I'd like to have something approximating a split view with wiki text on one side and an approximate...
I've had a look at how to implement this myself, and it seems that I would have to pass in the HTTP Basic authenticator to the wiki class. This would...
That seems fine. Explicit being better than implicit and all that. My only thought is whether AWS is moving to the lowercase example for future APIs. In which case a...
A further thought after sleeping in it: at the moment, if the lowercase `tags` key is present, then the existing `TagsField` will silently fail to include the tags. It feels...
One issue with a blanket "continue on error" approach would be that `ResourceLinkFields` could error if their target wasn't scanned. They would need to be converted into `TransientResourceLinkFields` in some...