January 2018 – Josh Anthony

React Error: Expected a string, got object

Posted on January 27, 2018Leave a comment

If you’re working with React, you might run into one or both of these errors:

Warning: React.createElement: type should not be null, undefined, boolean, or number. It should be a string (for DOM elements) or a ReactClass (for composite components). Check the render method of `SomeComponent`.
bundle.js%20line%20242%20%3E%20eval:45:9

Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object. Check the render method of `SomeComponent`.

One possible problem, which is what happened to me, is that you simply forgot to export one of your modules. In this case, I had a child component which I forgot to export, but the resulting error said nothing about the child component so it took awhile to puzzle this out. Hopefully this helps someone else figure out the problem faster than I!

Super Mario in the Real World

Posted on January 22, 2018Leave a comment

Here is a cool video I found of someone who recreated the first level of Super Mario Bros in augmented reality!

Is it an AAA-caliber game? No, obviously, but it is an impressive tech demo and a sign of what AR can bring to the world.

Laravel Redirect Status Code

Posted on January 2, 2018Leave a comment

Laravel’s documentation doesn’t make this obvious, but when you are using a redirect you can change what the status code of the redirect is.

Route::get('some/route', function(){
    return Redirect::to("another/route", 301);
});

Route::get('some/route', function(){
    return Redirect::route("another.route", null, 301);
});

The tricky part is knowing which parameter is the status code. To check which parameter it is, refer to the Redirector Class.