7 Commits (4b76af2521255a3640ff9a91f0f70b8929a4b617)

Author	SHA1	Message	Date
Oliver Günther	7758812768	[25387] Refactor query availabe states into separate input states (#5659) ... * Refactor query availabe states into separate input states * Fix tests [ci skip]	7 years ago
ulferts	f4b36edccb	Feature/save zoom in query 7 1 (#5637) ... * Implement timeline zoom level as query enum * Implement query zoom handling in frontend Had to refactor: 1. The zoom level enum in the frontend cannot properly be matched to strings so I chose a separate type instead to map to the string retrieved from /sent to the query 2. The way query updates are done through the states. The previous implementation only worked for one single attribute state. For the timeline state, it does not make sense to split that into two, so I delegate to the state to handle checking and updating the query. * Extend feature spec for zoom saving * Refactor URLParamsHelper into TS service * Fix comparison in table query services * Remove reference to allowedValues [ci skip]	8 years ago
Oliver Günther	568518d6a3	Move QueryColumn interface into its own class	8 years ago
Oliver Günther	7d62d846a2	Implement relation columns as secondary render pass	8 years ago
Oliver Günther	c2d050e5ba	Fix comparison in table query services	8 years ago
Oliver Günther	d6b8b92037	Implement query zoom handling in frontend ... Had to refactor: 1. The zoom level enum in the frontend cannot properly be matched to strings so I chose a separate type instead to map to the string retrieved from /sent to the query 2. The way query updates are done through the states. The previous implementation only worked for one single attribute state. For the timeline state, it does not make sense to split that into two, so I delegate to the state to handle checking and updating the query.	8 years ago
Oliver Günther	90c6fdfed6	Move comparer and extractor functions into state value classes ... This clears up what the controller has to do and allows us to double check 1. The previous value of the state has changed 2. IF (1) is true, whether the query value for that attribute is changed We need to check the second part additionally since the states may be updated as a result of the query being updated in `wpListService.updateStatesFromQuery` The 'correct' solution here would be to create two input states, and a dependent state that executes resulting actions.	8 years ago
Jens Ulferts	86109480ae	replace experimental by v3 in wp list	8 years ago