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

sparse decoration warning is unclear #2546

Closed
levBagryansky opened this issue Oct 17, 2023 · 9 comments · Fixed by #2673
Closed

sparse decoration warning is unclear #2546

levBagryansky opened this issue Oct 17, 2023 · 9 comments · Fixed by #2673
Assignees
Milestone

Comments

@levBagryansky
Copy link
Member

levBagryansky commented Oct 17, 2023

Now sparse decoration warning looks like```

[INFO] Shift #0 via 'globals-to-abstracts' made no changes
[INFO] Shift #0 via 'globals-to-abstracts' made no changes
[INFO] Shift #0 via 'globals-to-abstracts' made no changes
Error:  net.sf.saxon.style.XSLText@62f2a4fe: Warnings identified: Sparse decoration is prohibited; 
Error:  #fatalError(): Processing terminated by xsl:message at line 32 in fail-on-warnings.xsl; SystemID: file:///org/eolang/parser/fail-on-warnings.xsl; Line#: 32; Column#: 17
[INFO] Shift #0 via 'globals-to-abstracts' made no changes
[INFO] Shift #0 via 'globals-to-abstracts' made no changes

So it does not provide information in which .eo file the mistake happened. Let's expand it

@levBagryansky
Copy link
Member Author

@maxonfjvipon WDYT?

@maxonfjvipon
Copy link
Member

@levBagryansky it's not about only sparse-decoration warning. It's about all warnings at all. Replace sparse-decoration with any other warning and you get the same story.
And you're right, it would be nice to extend the log info
Want to take it on?

@levBagryansky
Copy link
Member Author

@maxonfjvipon yes, let me try

@maxonfjvipon
Copy link
Member

@levBagryansky sure, go ahead

@Graur Graur added this to the Important milestone Oct 30, 2023
levBagryansky added a commit to levBagryansky/eo that referenced this issue Dec 4, 2023
levBagryansky added a commit to levBagryansky/eo that referenced this issue Dec 4, 2023
levBagryansky added a commit to levBagryansky/eo that referenced this issue Dec 5, 2023
@0pdd
Copy link

0pdd commented Dec 5, 2023

@levBagryansky the puzzle #2674 is still not solved.

@0pdd
Copy link

0pdd commented Dec 28, 2023

@levBagryansky 2 puzzles #2746, #2747 are still not solved; solved: #2674.

@0pdd
Copy link

0pdd commented Jan 9, 2024

@levBagryansky 2 puzzles #2747, #2764 are still not solved; solved: #2674, #2746.

@0pdd
Copy link

0pdd commented Jan 17, 2024

@levBagryansky 3 puzzles #2747, #2790, #2791 are still not solved; solved: #2674, #2746, #2764.

@0pdd
Copy link

0pdd commented Jan 26, 2024

@levBagryansky 4 puzzles #2747, #2820, #2821, #2822 are still not solved; solved: #2674, #2746, #2764, #2790, #2791.

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

Successfully merging a pull request may close this issue.

4 participants