@igorim
iamme
Nothing here yet.
Nothing here yet.
No blogs yet.
Can you give an example of what type of expressions you're talking about? We actually just built one, so I can definitely share some insight, but just want to make sure we are on the same page :)
The easiest is in your submit call iterate over the array and validate each object, if pass continue if fail display validation and exit submit action before sending data. Example: let dataArray = [{id1: {valid: true }}, {id2: {valid: false }}, {id3: {valid: true }}, {id4: {valid: false }}, {id5: {valid: true }}] let validations = {} dataArray.map((v,i) => { if (! Object .keys(v)[ 0 ].valid) validations[ Object .keys(v)[ 0 ]] = true } adjust above to your use case In your Redux state you'd have a validation slice which would be replaced by the validations object above. In the component you'd have something like { this .props.validations && this .props.validations[identifier] ? <Error /> : null }
I generally use Apache 2.0. I feel it's a pretty open one allowing you to use it for personal or commercial, while not necessarily requiring recontribution. The recontribution clause (a la GPL) is what stops most companies from using GPL packages. I fully believe it is very important for people to recontribute back to the community, but I also realize that we live in a real world and some code is proprietary and should not be exposed outside of the business, so forcing someone to just doesn't seem right
It depends on what you use to define hottest. Most paying? depending on the market it definitely is up there. Most Challenging? It depends, there are definitely more challenging things than frontend, but in today's climate you definitely shouldn't bored. Career Prospects, job security? Job security is most likely, although if you do your job right you're digging into your own job security lol Career prospects are questionable, 90% of companies still don't have front end architects, and I'm not aware of many Principal engineers who come from frontend, so after Senior you're kinda stuck. Hopefully that'll change soon
for simple feature 3 frameworks and 3MBs used, developers are not thinking, just copy pasting... I think you nailed it right there. The problem isn't the ecosystem, it partially does contribute, but it is largely the inability to understand what to use for what problem. To be fair it's a hard decision to make usually, even experienced engineers get it wrong OFTEN. Most frameworks and tools are great at solving specific problems and once you face that problem those tools are a godsend. The problem I see is people try to overcomplicate things and use these tools where they aren't really needed (says a guy who wrote a personal site in react :/) Another reason for the craziness is that you're working with a single language for the whole internet population. In the backend world there are a dozen of languages, each of which has gone through the same problems at a slower rate, smaller audience. With frontend there is one, and a few years ago everyone suddenly started caring about it, so you got 10+ years of innovation over a dozen languages/ecosystems packed into 3, of course it'll get crazy. Contrary to what a lot of people feel it's a good thing. Innovation drives progress forward and propels new ideas into the open. To keep sane just stick to a few frameworks/tools you may need and know them on a high level, if you have a project that would benefit from one them learn them deeply. If you have a project that doesn't feel right with the ones you know, look for a new one or write one that solves that problem It is impossible to learn everything, just learn enough to make yourself be effective at getting the project done
C++ has it's uses for sure, but the reason for not using it for web backends is that 95% of the times you don't need the performance that C++ offers. What you do get is a maintainability nightmare, features taking months vs days to release and a shortage of talent.