Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Taxonomy directory - problems to be solved #55

Open
robbieaverill opened this issue Apr 15, 2018 · 1 comment
Open

Taxonomy directory - problems to be solved #55

robbieaverill opened this issue Apr 15, 2018 · 1 comment

Comments

@robbieaverill
Copy link
Contributor

robbieaverill commented Apr 15, 2018

I've just had a look at the TaxonomyDirectorController in the context of CWP 2.0. Here are some issues I've noticed:

I actually think that this class shouldn't be in this module - BasePage is specific to CWP, and this logic should live in the cwp/cwp module or something similar.

I think we should deprecate the class and move it back to a documentation only example. If it should live in CWP then we can add it to CWP later on. Thoughts?

@NightJar
Copy link
Contributor

NightJar commented Apr 16, 2018

The PR is #45 (comment) with the comment thread in question (which is aimed to supercede #40 by the PR description).

I feel like dot notation can solve the issue of the phantom BasePage, and remove the innerJoin custom query logic. This is particularly helpful in SS4 with different/adaptive/settable table names.
The dot notation reference can be built by a relation lookup, which can be defined via injector service definitions.

Caveat that I've not thought too deeply about this yet. Just initial thoughts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants