Filter
Exclude
Time range
-
Near
unknown retweeted
CM anadhum Joseph vijay enum naan ah post pannirundha reach noruki vitrukalam 😭πŸ”₯ Indha jega edhuku dhan irukano!
19
123
870
18,920
Replying to @Raghul_018
Apo nenjam enum oorinile illayaa 🀧πŸ₯²πŸ˜­
1
83
Day 140 Backend Enum validation - status and priority now reject anything outside defined values Field validator - whitespaceonly titles return 422 before touching the DB Global exception handler - every error returns consistent JSON Query filters for Status and Priority
Day 139 Backend Full Task CRUD - create, read, update, patch status, delete JWT-protected routes - unauthenticated requests get 401, wrong user gets 404 Enum validation on status & priority - "YOLO" gets rejected before it touches the DB Ownership boundary Backend is Hard
4
8
73
Deva ✰ CπŸ•ΆοΈlie retweeted
You are in the wrong INDUSTRY @Dir_Lokesh. KW audience enum vetti Puluthi pumdainga athigam...
Loki in Karuppu πŸ˜†πŸ’₯
1
2
14
475
Suppose you have a Map<AssetId, Position>. If this is generalized to Map<u64Key, Opaque64ByteEntry>, you can enforce on the interface level that certain integer ranges of the key correspond only to Positions, and the opaque types will be transmuted under the hood. You can now safely use this container to store other object types as long as the key space is carefully defined and the interface is correctly implemented! With Lists, it’s even easier because you can reserve discriminant bytes on the inner object itself (everything by default becomes an Enum)
3
412
Dai neinga enum 50 varusathuku vara madingabda πŸ€¦β€β™‚οΈ
8