I can certainly test this. My question would then be, will this result in actually mapping a null in the dto, or would the .ExampleProperty? just “be null” and cause the long property to instantiate to 0?
I can certainly test this. My question would then be, will this result in actually mapping a null in the dto, or would the .ExampleProperty? just “be null” and cause the long property to instantiate to 0?
At first “glance”, if you’re looking to get into DevOps, then a deployment engineer should be a good match. I suppose it depends on the company and what they really want vs the job req description. As a Release Engineer, you would need to have (or get on the job) skills with CI/CD pipelines (build/release), branch management and release merging/tagging, and so on. Again, it depends what the company is really doing or wanting from that role.
You could do a series and post it to the [email protected] community. Or are you looking to have a separate community specifically focused on learning and such that isn’t mixed in with all the other c# topics and discussions?
I like option 1 and option 2. Option 2 seems easier to differentiate, as others have mentioned.
I enjoy Nick Chapsas videos as @[email protected] mentions. Other videos that pop up end up being “day in the life” type stuff rather than instructional/information content.
So… When I change…
.ForMember(ee => ee.ExampleId, options => options.MapFrom(ed => ed.ExampleProperty != null ? ed.ExampleProperty.ExampleId : (long?)null))
TO:
.ForMember(ee => ee.ExampleId, options => options.MapFrom(ed => ed.ExampleProperty?.ExampleId))
I am presented with: CS8072 - An expression tree lambda may not contain a null propagating operator.