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

Calculus.java:39-50: The node method in this interface... #511

Open
0pdd opened this issue Feb 5, 2021 · 0 comments
Open

Calculus.java:39-50: The node method in this interface... #511

0pdd opened this issue Feb 5, 2021 · 0 comments

Comments

@0pdd
Copy link
Collaborator

0pdd commented Feb 5, 2021

The puzzle 449-96cd40b8 from #449 has to be resolved:

* @todo #449:30min The `node` method in this interface was designed with only
* XSL implementation in mind - it uses the `metric` parameter to select the
* XSL file and uses that file to transform the `skeleton`. This makes Java
* based implementations a little awkward because the `metric` parameter
* becomes redundant: there is a Java implementation for each metric, and these
* implementations already know which metric they are for. The question becomes
* - how to select correct java implementation for a given metric and integrate
* it seamlessly with XSL calculus in `XslReport`. One option could be removing
* the `metric` parameter from the method and injecting a Calculus for a
* concrete metric in `XslReport` directly. Another could be implementing
* Chain Of Responsibility pattern. Decide on the best way to integrate Java
* based Calculus with XSL based Calculus in `XslReport` and implement it.

The puzzle was created by yegor256 on 05-Feb-21.

Estimate: 30 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

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

2 participants