package-info.java:38-41: Continue applying the new class...

[0pdd]

The puzzle 964-1a0e1078 from #964 has to be resolved:

cactoos/src/main/java/org/cactoos/package-info.java

Lines 38 to 41 in be02845

	* @todo #964:30min Continue applying the new class naming convention in effect:
	* avoid compound names for decorators. Continue renaming classes according to
	* this table: https://github.com/yegor256/cactoos/issues/913#issuecomment-402332247.
	* Remaining packages are scalar, set, text, and time.

The puzzle was created by George Aristy on 20-Dec-18.

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.

[0pdd]

This puzzle inherited milestone 1.0 from issue #964.

[0crat]

@llorllale/z please, pay attention to this issue

[0crat]

Job #980 is now in scope, role is DEV

[0crat]

The job #980 assigned to @dgroup/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

[0crat]

Job gh:yegor256/cactoos#980 already assigned to @dgroup, can't assign to @dgroup

[dgroup]

@0crat wait as clarification is required for this task.

[0crat]

@0crat wait as clarification is required for this task. (here)

@dgroup The impediment for #980 was registered successfully by @dgroup/z

[dgroup]

@llorllale, as i understood we need to rename the classes from the following packages in order to avoid compound names:

• scalar
• set
• text
• time

Do we need to rename the *Envelope classes?

Also, as far as I can see there are a lot of implementations of Bytes present in *.io package and has the same problem like CheckedBytes, UncheckedBytes, etc.
What should be done with them?

I would like to highlight that in order to avoid the compound names all implementations of Input, Output, Bytes, Func, BiFunc, Proc, BiProc, Scalar, Text should have their own packages.
Now, the some of implementation of Bytes, Input, Output shuffled between packages org.cactoos.io, org.cactoos.bytes.
We can fix that by changing our packages structure to

org.cactoos.io
|- bytes
|- input
|- output

Similar situation with Func, BiProc and BiFunc.

[llorllale]

@dgroup

Also, as far as I can see there are a lot of implementations of Bytes present in *.io package and has the same problem like CheckedBytes, UncheckedBytes, etc.
What should be done with them?

The general rule is to avoid compound names, yes, but sometimes technical limitations force us to keep using them in some cases. For example, there are more than one classes with the Checked prefix in their names in the io package. Removing the suffix would create a naming conflict. If you see any remaining classes in the io package or anywhere else with compound names that can be simplified without causing conflicts, please go ahead and refactor.

Do we need to rename the *Envelope classes?

I don't think we need to rename the *Envelopes. It's a special naming convention that communicates something about those classes.

I would like to highlight that in order to avoid the compound names all implementations of Input, Output, Bytes, Func, BiFunc, Proc, BiProc, Scalar, Text should have their own packages.

I'm not convinced it's worth it. Would be better to discuss in a separate ticket.

[0pdd]

The puzzle 964-1a0e1078 has disappeared from the source code, that's why I closed this issue.

[0pdd]

@0pdd 5 puzzles #1003, #1004, #1005, #1006, #1007 are still not solved.

[0crat]

The job #980 is now out of scope

[0crat]

Order was finished: +30 point(s) just awarded to @dgroup/z

[0pdd]

@0pdd 4 puzzles #1003, #1005, #1006, #1007 are still not solved; solved: #1004.

[0pdd]

@0pdd 4 puzzles #1003, #1005, #1006, #1025 are still not solved; solved: #1004, #1007.

[0pdd]

@0pdd 4 puzzles #1003, #1005, #1025, #1046 are still not solved; solved: #1004, #1006, #1007.

[0pdd]

@0pdd 5 puzzles #1003, #1025, #1046, #1064, #1065 are still not solved; solved: #1004, #1005, #1006, #1007.

[0pdd]

@0pdd 5 puzzles #1003, #1025, #1046, #1064, #1074 are still not solved; solved: #1004, #1005, #1006, #1007, #1065.

[0pdd]

@0pdd 4 puzzles #1003, #1025, #1046, #1074 are still not solved; solved: #1004, #1005, #1006, #1007, #1064, #1065.

[0pdd]

@0pdd 3 puzzles #1003, #1025, #1046 are still not solved; solved: #1004, #1005, #1006, #1007, #1064, #1065, #1074.

[0pdd]

@0pdd the puzzle #1046 is still not solved; solved: #1003, #1004, #1005, #1006, #1007, #1025, #1064, #1065, #1074.

[0pdd]

@0pdd all 10 puzzles are solved here: #1003, #1004, #1005, #1006, #1007, #1025, #1046, #1064, #1065, #1074.