| # Inspired from http://blog.hio.fr/2011/09/17/doctrine2-yaml-mapping-example.html | |
| MyEntity: | |
| type: entity | |
| repositoryClass: MyRepositoryClass | |
| table: my_entity | |
| namedQueries: | |
| all: "SELECT u FROM __CLASS__ u" | |
| # Class-Table-Inheritance |
| /* | |
| * | |
| * A simple JavaScript dependency injection container | |
| * By Monroe Thomas http://blog.coolmuse.com | |
| * | |
| * http://blog.coolmuse.com/2012/11/11/a-simple-javascript-dependency-injection-container/ | |
| * | |
| * MIT Licensed. | |
| * | |
| * Unit tests can be found at https://gist.github.com/4270523 |
| <?php | |
| /** | |
| * The below functions take the single level array of items as an argument | |
| * and turn it into a multidimensional array structure (tree), | |
| * where each item has an array of sub-items. | |
| * | |
| * Each item should have at least an `id` and `parent_id`, | |
| * where the `parent_id` is `0` if it's top level. | |
| * | |
| * Source: http://goo.gl/p2GybZ |
| <!doctype html> | |
| <html ng-app="Demo"> | |
| <head> | |
| <meta charset="utf-8" /> | |
| <title> | |
| Loading AngularJS Components After Application Bootstrap | |
| </title> | |
| <style type="text/css"> |
| # delete local tag '12345' | |
| git tag -d 12345 | |
| # delete remote tag '12345' (eg, GitHub version too) | |
| git push origin :refs/tags/12345 | |
| # alternative approach | |
| git push --delete origin tagName | |
| git tag -d tagName |
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');Those suck for maintenance and they're ugly.
| 'use strict'; | |
| // simple express server | |
| var express = require('express'); | |
| var app = express(); | |
| var router = express.Router(); | |
| app.use(express.static('public')); | |
| app.get('/', function(req, res) { | |
| res.sendfile('./public/index.html'); |
| .wrapper{ | |
| width: 550px; | |
| text-align: justify; | |
| background: firebrick; | |
| font-size: 0; | |
| font-size: 12px\9; /* IE6-9 only hack */ | |
| } | |
| .wrapper div{ | |
| background: white; |
| Quick tip for handling CSRF Token Expiration - common issue is when you use csrf protection is that if | |
| a form sits there for a while (like a login form, but any the same) the csrf token in the form will | |
| expire & throw a strange error. | |
| Handling it is simple, and is a good lesson for dealing with other types of errors in a custom manner. | |
| In Middleware you will see a file VerifyCsrfToken.php and be tempted to handle things there. DON'T! | |
| Instead, look at your app/Exceptions/Handler.php, at the render($request, Exception $e) function. | |
| All of your exceptions go through here, unless you have excluded them in the $dontReport array at the |
You should use merge operation on entities which are in detached state and you want to put them to managed state.
Merging should be done like this $entity = $em->merge($detachedEntity). After that $entity refers to the fully managed copy returned by the merge operation. Therefore if your $form contains detached entities, you should adjust your code like this:
$doctrineManager = $this->getDoctrine()->getManager();
foreach ($form->getData()->getEntities() as $detachedEntity) {
$entity = $doctrineManager->merge($detachedEntity);
$doctrineManager->remove($entity);
}
$doctrineManager->flush();