Fix for FOUC :
At the top of your HTML:
<!doctype html>
<html>
<head>
<style>html{visibility: hidden;opacity:0;}</style>
Fix for FOUC :
At the top of your HTML:
<!doctype html>
<html>
<head>
<style>html{visibility: hidden;opacity:0;}</style>
| SET @database_current = '<production>'; | |
| SET @database_dev = '<development>'; | |
| -- column and datatype comparison | |
| SELECT a.TABLE_NAME, a.COLUMN_NAME, a.DATA_TYPE, a.CHARACTER_MAXIMUM_LENGTH, | |
| b.COLUMN_NAME, b.DATA_TYPE, b.CHARACTER_MAXIMUM_LENGTH | |
| FROM information_schema.COLUMNS a | |
| LEFT JOIN information_schema.COLUMNS b ON b.COLUMN_NAME = a.COLUMN_NAME | |
| AND b.TABLE_NAME = a.TABLE_NAME | |
| AND b.TABLE_SCHEMA = @database_current | |
| WHERE a.TABLE_SCHEMA = @database_dev |
initialize: once, when the controller is first instantiatedconnect: anytime the controller is connected to the DOM| .m-notifications { | |
| position: fixed; | |
| bottom: 20px; | |
| right: 20px; | |
| display: flex; | |
| flex-direction: column; | |
| align-items: flex-end; | |
| z-index: 10; | |
| .m-notification { |
| //https://stackoverflow.com/questions/1179672/how-to-avoid-installing-unlimited-strength-jce-policy-files-when-deploying-an | |
| private static void removeCryptographyRestrictions() { | |
| if (!isRestrictedCryptography()) { | |
| return; | |
| } | |
| try { | |
| /* | |
| * Do the following, but with reflection to bypass access checks: | |
| * | |
| * JceSecurity.isRestricted = false; JceSecurity.defaultPolicy.perms.clear(); |
| FROM php:7.1-fpm-alpine | |
| RUN apk add --update \ | |
| autoconf \ | |
| g++ \ | |
| libtool \ | |
| make \ | |
| && docker-php-ext-install mbstring \ | |
| && docker-php-ext-install mysqli \ |
The Qt framework offers Qt Test / QTestLib as a simple unit-testing framework for Qt-based projects. Perhaps too simple, as it comes with an annoying limitation that requires a separate executable for each test class, or creating a single test runner with a manually added call to each test suite.
A quick search shows easy and helpful workarounds that offer to replace the manual work with a short #include and a macro. Then the test-runner remains untouched and finds all your test suites with these hints alone.
1]: http://qtcreator.blogspot.co.il/2009/10/running-multiple-unit-tests.html
2]: https://marcoarena.wordpress.com/2012/06/23/increase-your-qtest-productivity/
3]: https://github.com/e-j/qt-multiple-tests
In version 4.0 of QtCreator, the AutoTest plugin is made available to all, through the Community Edition of QtCreator. It offers a decent “Test Results” output pane that allows you to run and monitor th
| <?php | |
| namespace MyProject\Cli\Command; | |
| use Symfony\Component\Console\Input\InputInterface; | |
| use Symfony\Component\Console\Input\InputOption; | |
| use Symfony\Component\Console\Output\OutputInterface; | |
| class DbMigrate extends \Symfony\Component\Console\Command\Command | |
| { |