Aidan Harbison

This is perfect, thank you! Admittedly I did search through the docs before opening this, but somehow missed this. Thanks for the quick response, and as always excellent documentation.

Re-opening for a related query, then happy to close again. It does not appear that `JustAfterEach` is usable from the context of `BeforeSuite` or `AfterSuite`, so what is the recommended...

In addition to this, I think it would be beneficial to offer a word-wrap toggle, so that horizontal scrolling could be disabled. For example, it's not a great user experience...

Doing a bit of testing, and it seems a trigger for this behavior is the presence of the slug in the link. So for example, this would reproduce the issue:...

To add to this, I forgot to mention that in order for the auto-generation to be configured for the PK column, I had to run: ``` npm run migrate --...

Sorry for this going stale. I would be interested in submitting this patch. I will try to find some time to get this done.

I've been tinkering with this, and I'm a little torn on how to handle this. Technically, moving from a property defined by: ```js properties = { example: { type: Number...

For reference, the I've added a test case (that fails currently) to demonstrate this bug. Implementing the change should allow the test case to pass. https://github.com/aharbis/loopback-connector-postgresql/commit/d3f16e3e8dcf9b02536a9c30cdf8102c3410f369

Thinking a little more on this. The original issue I reported was focused on the behavior with the `PRIMARY KEY`. I don't think PostgreSQL handles the `SERIAL` type any different...

Actually, this may not be scoped to just those middlewares. I am also seeing similar behavior for other routes, where neither of the NotFound nor MethodNotFound handlers were involved.