Giter Site home page Giter Site logo

Classes are too bulky about jadventure HOT 5 CLOSED

progether avatar progether commented on August 24, 2024
Classes are too bulky

from jadventure.

Comments (5)

verhagen avatar verhagen commented on August 24, 2024

Have a look in my improve-code branch as well, I've done the same as well.

from jadventure.

projectdelphai avatar projectdelphai commented on August 24, 2024

@verhagen unfortunately I've had to come to the conclusion that your improve-code branch is way too big for me to look through. With 100 commits ahead and 20+ commits behind master, I can't differentiate which is the same, which is behind, and which is ahead. So honestly your best bet is to start multiple branches which deal with different issues and connect those specific branches as pull requests with specific issues. As it is right now, not only is the improve-code branch too big, it also contains many controversial changes which we may not want to be implemented. Now I and some of the other maintainers (i.e @hawk554 or @indivisible-irl ) could go through and git cherry-pick the specific commits but honestly it's just much easier to leave it alone and let those changes come in organically one at a time.

Sorry but unless someone is willing to fork your branch, fix all the merge conflict and then separate all the commits apart, it's gonna be too difficult to merge.

from jadventure.

projectdelphai avatar projectdelphai commented on August 24, 2024

fixed.

from jadventure.

verhagen avatar verhagen commented on August 24, 2024

I think several of the changes, done in these last 20 commits, I did fix already as well, in the improve-code branch.
There are more test and the code is a lot cleaner I think. Have a look through the issues I resolved to get an idea.
Indeed merging is not easy, I do understand that as well. Is it possible the pull my branch in, check which of the 20 commits have not been resolved in the improve-code branch, re-do them there and then merge the improve-code into master.

from jadventure.

projectdelphai avatar projectdelphai commented on August 24, 2024
  1. I think your link to the resolved issues is wrong.
  2. Yes, it's possible but not worth it and not (as I believe) good practice. Rather, it is better to cherry pick from your branch what hasn't been fixed into master and only merge those. We merge from outside in and not inside out and then back again. Too much confusion.
  3. And unfortunately, even if you did fix them, they're not recognized as valid fixes until a patch is requested and merged.

from jadventure.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.