email:string( regex(".*@.*\\..*") ) This is incorrect regex for email. The correct one is https://pdw.ex-parrot.com/Mail-RFC822-Address.html
It's a pragmatic one. It has no false negatives, and there's rarely a reason to care about false positives. (Especially not where a stricter regex would (be the only mechanism to) catch it, but a fake-but-valid address wouldn't trivially bypass it.)
Jolie, the service-oriented programming language
31–40 of 62 posts
Re: Jolie, the service-oriented programming language
#32Earlier quoted context omitted.
At a certain point I think you're allowed to say you don't care if the person with this email address is capable of signing up or using your service: very.”(),:; []”.VERY.”very@\\ "very”.unusual@strange.example.com
Too bad - if that's my email address and you're rejecting it, I'm going to sue you for denying service arbitrarily and win. Not every country is the USA.
Which country are you claiming this entirely implausible legal scenario would work in?
Re: Jolie, the service-oriented programming language
#33I was kinda forced to use it for an university exam. The premise was interesting but working with it was bad. Maybe it improved in the last 5/6 years, but I doubt it's used for many (or any) real use case.
Re: Jolie, the service-oriented programming language
#34Re: Jolie, the service-oriented programming language
#351. A contract-first language where all of your queries (reads) and mutations (writes) are defined in the GraphQL type language.
2. Refinement types can be implemented with directives or custom scalars.
3. The "built for the networked age" section is very similar to what Apollo Federation gives you - the ability to move implementations of part of your GraphQL API service to different servers with end clients being unaware.
4. Protocol agnositic - technically GraphQL is protocol agnostic but in really nobody cares because everyone uses HTTP or Websockets.
Re: Jolie, the service-oriented programming language
#36Earlier quoted context omitted.
That is an absurdly complex regex
Email address specs turn out to be rather complicated. I really wish people wouldn't code their own checks rather than use already existing standards. Some languages like Java even include proper checks in their standard library: https://java.net/projects/javamail Several jobs back I had no end of arguments with some Java devs about not writing their own checks, that kept routinely failing on legitimate addresses.
Re: Jolie, the service-oriented programming language
#37Earlier quoted context omitted.
For those who don't know, jolie means pretty in french, and is a common woman's name.
I don't think I've heard heard of someone named Jolie. According to data from INSEE (France's Census Bureau equivalent), since 1925, only 6 babies were named Jolie in 2011 and then 5 more in 2018. There's a Joline which you'd pronounce pretty much like jolie as the n is very weak, but it's barely more popular. Anyway, jolie does mean pretty, but it's not really a name (11~0 at this scale).
Re: Jolie, the service-oriented programming language
#38email:string( regex(".*@.*\\..*") ) This is incorrect regex for email. The correct one is https://pdw.ex-parrot.com/Mail-RFC822-Address.html
That is an absurdly complex regex
Re: Jolie, the service-oriented programming language
#39I think it would be better if this was a code generator similar to `protoc` for gRPC, so we don't have to learn yet another implementation language.
Specifically, you'll be able to use Jolie to write (tech-agnostic) APIs and then implement them in Java, using types automatically generated from the Jolie APIs.
Re: Jolie, the service-oriented programming language
#40email:string( regex(".*@.*\\..*") ) This is incorrect regex for email. The correct one is https://pdw.ex-parrot.com/Mail-RFC822-Address.html
It's a pragmatic one. It has no false negatives, and there's rarely a reason to care about false positives. (Especially not where a stricter regex would (be the only mechanism to) catch it, but a fake-but-valid address wouldn't trivially bypass it.)