New React front end

[jochenklar]

This PR implements a new React front end, replacing AngularJS.

[coveralls]

Pull Request Test Coverage Report for Build 9178299879

Details

• 18 of 18 (100.0%) changed or added relevant lines in 6 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.07%) to 64.052%

---

Totals
Change from base Build 8016830665:	0.07%
Covered Lines:	4834
Relevant Lines:	7547

---

💛 - Coveralls

[kimakan]

@jochenklar I've encountered a strange bug in the schemas dropdown. In short, sometimes clicks on the columns change the active schema and table which is unexpected. Specifically, it jumps to a user table if a column with the same name as the clicked column exists there. The clicked column should not have an effect on the listed schemas and tables.
afaik, the issue comes from the function updateBrowser

daiquiri/daiquiri/metadata/assets/js/components/Schemas.js

Line 34 in 7cb39a6

const updateBrowser = () => {

In particular, I don't really understand the reason for the following piece of code

daiquiri/daiquiri/metadata/assets/js/components/Schemas.js

Lines 66 to 71 in 7cb39a6

	} else if (activeItem.type == 'column') {
	// search for the schema and the table for the column
	const [schema, table] = schemas.reduce((result, schema) => {
	const table = (schema.tables || []).find(t => (t.columns && t.columns.find(c => isEqual(c, activeItem))))
	return isNil(table) ? result : [schema, table]
	}, [])

Are you searching for schemas and tables that contain the clicked column? why?

I'm trying to fix it myself, so I just need a few pointers to understand the reasoning for the current implementation better :-).

[kimakan]

The bug seems to be fixed if the 'column' branch of the 'if-else' remains empty.

} else if (activeItem.type == 'column') { }

As of now, I don't see that anything else got broken because of this fix.

[jochenklar]

Hi @kimakan , I answer in #254.