我正在使用{{ dump(foo) }}Twig中的函数来调试我的模板.但是,如果模板在dump()函数之后抛出错误,您将只看到Symfony的调试页面,通知您错误.您可以明显地在Twig模板中注释掉有问题的代码行,但是有一种方法可以立即终止模板的执行,这样dump()函数的输出就是屏幕上打印的最后一个东西.我天真地想着类似的东西{{ dump(foo) }} {{ die() }}.关于如何实现这一目标的任何想法?
jest.fn()我对从使用创建的干净 CRA 项目运行时的以下行为感到困惑npx create-react-app jest-fn-behaviour。
例子:
describe("jest.fn behaviour", () => {
const getFunc = async () => {
return new Promise((res) => {
setTimeout(() => {
res("some-response");
}, 500)
});;
}
const getFuncOuterMock = jest.fn(getFunc);
test("works fine", async () => {
const getFuncInnerMock = jest.fn(getFunc);
const result = await getFuncInnerMock();
expect(result).toBe("some-response"); // passes
})
test("does not work", async () => {
const result = await getFuncOuterMock();
expect(result).toBe("some-response"); // fails - Received: undefined
})
});
Run Code Online (Sandbox Code Playgroud)
上述测试将在干净的 JavaScript 项目中按预期工作,但在 …
我在Symfony 2中使用以下Monolog配置来记录/app/logs/目录中文件中的较小错误,并发送电子邮件以查找所有严重错误.
monolog:
handlers:
main:
level: error
type: stream
path: "%kernel.logs_dir%/%kernel.environment%_remaining.log"
channels: ["!doctrine", "!request", "!security"]
request:
type: fingers_crossed
handler: requests
requests:
type: group
members: [request_critical, request_error]
request_critical:
level: critical
type: stream
path: "%kernel.logs_dir%/%kernel.environment%_request_critical.log"
channels: [request]
request_error:
level: error
type: stream
path: "%kernel.logs_dir%/%kernel.environment%_request.log"
channels: [request]
doctrine:
level: error
type: stream
path: "%kernel.logs_dir%/%kernel.environment%_doctrine.log"
channels: [doctrine]
security:
level: error
type: stream
path: "%kernel.logs_dir%/%kernel.environment%_security.log"
channels: [security]
mail:
type: fingers_crossed
action_level: critical
handler: buffered
buffered:
type: buffer
handler: swift
swift:
type: swift_mailer
from_email: …Run Code Online (Sandbox Code Playgroud) symfony ×2
apache ×1
async-await ×1
javascript ×1
jestjs ×1
monolog ×1
php ×1
reactjs ×1
twig ×1