Opportunity to reduce amount of information transferred between client and server

[AlexeySachkov]

I've been writing some tests for /api POST route and I discovered that in response to newly created homebrewery document, server sends its gzip-ed content back to the client as well as the rest of metadata. However in newPage we immediately redirect user to edit page without even using this information:

homebrewery/client/homebrew/pages/newPage/newPage.jsx

Lines 108 to 123 in ba600f5

	request.post('/api')
	.send(_.merge({}, this.state.metadata, {
	text : this.state.text
	}))
	.end((err, res)=>{
	if(err){
	this.setState({
	isSaving : false
	});
	return;
	}
	window.onbeforeunload = function(){};
	const brew = res.body;
	localStorage.removeItem(KEY);
	window.location = `/edit/${brew.editId}`;
	});

I don't think that this is an issue with huge impact, because most likely users press save on new brew page earlier than entering a lot of content in there, but still it makes sense to clean up our code

[5e-Cleric]

Given that we want to merge new and edit, i'd say this should keep sending the brew back. Keeping it for when we finally merge the two.

Linking #1800 as it tracks the unification of the two pages. Closing this.