ramona
ramona
Symfony translators looks first for messages.de_DE.yml, then messages.de.yml.
Yes, because it is the format that Symfony supports for its locale. Valid "lang" attribute value for tag is "de-DE".
LGTM, with one little exception. The correct format for lang attribute in HTML is en-GB, not en_GB (http://www.w3.org/TR/html5/dom.html#the-lang-and-xml:lang-attributes, http://www.ietf.org/rfc/bcp/bcp47.txt).
Is the complexity really worth the benefit? I mean, you can still call your constant `WHATEVER` and the tool won't complain. You can still do `const FIRST_COLOUR=1` and it'll pass...
So, I attempted implementing it, but there seems to be an issue - since StatementBuilder evaluates all the origins and all the destination before building the statement, and we need...
No worries, I'm also rather bust these days. The approach you're proposing sounds reasonable, I'll try it Soon™
Probably would require this to be done first: https://github.com/sfackler/rust-postgres/issues/116
What output would be expected from parsing UUIDs? I know those can be parsed into their respective fields, but that honestly doesn't seem all that useful in my opinion. Also,...
After a bit of investigation: It seems like the flow was not deployed. It would be useful if `server run` complained if no flows are deployed.
The libclang crash also happens on Gentoo. That's what I get when I run it under lldb: > Process 5968 stopped > - thread #7: tid = 6006, 0x00007fffea6042a0 libclangLex.so.3.8`clang::TokenLexer::Lex(clang::Token&)...