We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Instead, use the name of the parent if the bundle tag is modified, only the name of the fodler change.
The text was updated successfully, but these errors were encountered:
Mmmh, I understand, however this makes deserialization more painful (and frontend DTOs need the tag anyway).
Can we consider this as a low priority issue?
Sorry, something went wrong.
Yes.
Actually, the app works great. So lets implements things more necessary.
At worst, if it broke, we have some tests to find the bugs (I hope my tests cover the most used case)
On the other site, I don't understand why it's more painful ? Au contraire, and it'll be less IO consumer.
No branches or pull requests
Instead, use the name of the parent
if the bundle tag is modified, only the name of the fodler change.
The text was updated successfully, but these errors were encountered: