-
Notifications
You must be signed in to change notification settings - Fork 25
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
Tweak config and exception #91
Conversation
|
||
import kotlinx.serialization.SerializationException | ||
|
||
public sealed class TomlDecodingException(message: String) : SerializationException(message) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you have finally renamed it - may be make all exception's naming consistent? 😄
Let's select one of two variants:
- All of them are with 'Toml' prefix
- All of them are without a
Toml
prefix and only the base classTomlDecodingException
contains it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of them are without a
Toml
prefix and only the base classTomlDecodingException
contains it
I prefer this, and I imagine something like TomlEncodingException
for encoding. I'd like to make both of these as public
for users to manipulate, while actual exception types keep internal
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A further question: If there is only one file in exceptions
folder, I think to put it out along with Toml
and other stuff may be better, as that folder seems redundant.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer this, and I imagine something like TomlEncodingException for encoding
totally agree: TomlEncodingException
/TomlDecodingException
sounds very good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A further question: If there is only one file in exceptions folder, I think to put it out along with Toml and other stuff may be better, as that folder seems redundant.
Hm, but that will change package name. Instead of ktoml.exceptions.BlaBlaException - you will have ktoml.BlaBlaException. May be better to have it as is...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, but that will change package name. Instead of ktoml.exceptions.BlaBlaException - you will have ktoml.BlaBlaException. May be better to have it as is...
Then I'll have TomlEncodingException
in one file, and TomlDecodingException
another one.
Looks good, but it will completely break all users in the community 😭 😭 😭 Let's wait for #90 being merged... |
I have that in mind, so this problem could be solved later. Just put an |
Done.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, let's merge it after #90
and please fix diktat and detekt issues
If you don't mind - I will add you to this repo as a maintainer, so I won't need to approve CI/CD actions each time
diKTat errors this: |
created saveourtool/diktat#1170 and assigned on @Cheshiriks. I guess it should be fixed in the nearest future. @Peanuuutz could you please suppress this case with a |
If possible - could you please add the section |
I'm not good at paperwork so feel free to edit. :P |
ok, sure 😄 |
Sure 💪 |
oh, this branch is in fork. Never mind, I will open a new PR :) |
Update project
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed again. Ready to merge.
Merged, but as you are a maintainer of this repo, you can merge by yourself next time. But please use squash-merge |
here