Hello @steemthinkcom, thank you for considering my suggestion. @codingdefined did mention the rule:
Contributions must have a comprehensible commit history. Larger projects or updates submitted in a single commit will not be accepted.
This is for easier review of the changes done. So i think what you should have done here is make a commit of v1 (without the new features) as your initial/base codes, and another commit for the new features.
I also checked your commit history and i think it would have been best if you committed each feature in a separate pull requests to adhere to the rules.
And i would even suggest to publish a testable version of this app to give moderators the option to test the new features as well.
I support @codingdefined's decision here since I perceive that you overlooked the rule mentioned above.
hi @eastmael，thanks for you reply .
So, your suggestion is to resubmit this contribution as "new project" and provide a test version to facilitate the installation test?
Afterwards, new contributions will be submitted using "New Features" to facilitate mod review?
My suggestion is - do whatever you think is right with your project - focus on its development and adding value to it rather than adhering to rules just so that your contribution will be accepted.
I'm also suggesting to retain this contribution as is rahter than recreating and resubmitting it.
The reason being is that resubmitting it gives me the impression that your only resubmitting for it to be accepted, which is a complete waste of your and our time.
I understand that I will retain this contribution. The next IOS contribution will be based on this contribution.
Thank you for your understanding and looking forward to your next contributions.