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

OnReplaced.java:41-49: Frontend and backend delimiters... #2394

Closed
0pdd opened this issue Aug 15, 2023 · 8 comments · Fixed by #2408
Closed

OnReplaced.java:41-49: Frontend and backend delimiters... #2394

0pdd opened this issue Aug 15, 2023 · 8 comments · Fixed by #2408
Assignees
Milestone

Comments

@0pdd
Copy link

0pdd commented Aug 15, 2023

The puzzle 2376-11b46788 from #2376 has to be resolved:

* @todo #2376:90min Frontend and backend delimiters differ.
* I was confused with the delimiter '#' that we use in {@link OnReplaced} and delimiter which
* we use in the frontend. For example:
* - "org.eolang.text|0.1.0" - frontend
* - "org.eolang.text#0.1.0" - backend
* The problem here is that we use the '|' delimiter on the frontend and '#' in the backend, but
* both of them mean the same thing - object name + version.
* I believe that we need to use the same symbol in both places, because it will be easier to
* understand the code. So, my suggestion to use '|' in both places.

The puzzle was created by rultor on 15-Aug-23.

Estimate: 90 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.

@volodya-lombrozo
Copy link
Member

@Graur Why is this a Routine task? It influence the solution with versions significantly.

@Graur
Copy link
Contributor

Graur commented Aug 16, 2023

@volodya-lombrozo I agree that this task strongly affects the versioning task. However, this is a refactoring task, which is why it was given a low priority. We are trying to close older tasks and avoid cosmetic changes to recently committed code in order to reduce the number of issues created in the project. No one is trying to diminish the importance of this issue, we just think it would be better to focus on other tasks in the coming weeks. Perhaps I didn't fully understand the idea of the issue. If so please correct me.

@volodya-lombrozo
Copy link
Member

@Graur Yes, you are right. It is mostly a refactoring task, but it also involves an architectural violation. I would recommend solving it as soon as possible while the cost is lower. In a few months, this task will cost significantly more. However, I don't insist here.

@Graur
Copy link
Contributor

Graur commented Aug 17, 2023

@volodya-lombrozo Ok, let's make it happened

@0pdd
Copy link
Author

0pdd commented Aug 18, 2023

@0pdd the puzzle #2420 is still not solved.

@0pdd
Copy link
Author

0pdd commented Sep 1, 2023

@0pdd the puzzle #2463 is still not solved; solved: #2420.

@0pdd
Copy link
Author

0pdd commented Oct 17, 2023

@0pdd the puzzle #2544 is still not solved; solved: #2420, #2463.

@0pdd
Copy link
Author

0pdd commented Nov 20, 2023

@0pdd all 3 puzzles are solved here: #2420, #2463, #2544.

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

Successfully merging a pull request may close this issue.

3 participants