Skip to content

Tracking Issue: Codebase Cleanup #1395

@protocol-1903

Description

@protocol-1903

Goal

In this issue I plan on writing a bunch of things that I would like to work on eventually to make the codebase generally more sane, clean, and nicer to work around in and use.

Feedback

Feedback is welcomed by everyone.

Checklist guide

#1076

Emoji Description
Nothing I want to do it
I want to discuss with pydevs about if it will be good/okay
Potentially I will do

Checklist of Issues

  • Rename ree to raw-earth-ore
  • Unify all big rock names to be named <resource>-rock
    • sulfur-patch -> sulfer-rock
    • regolites - regolite-rock
    • bitumin-seep -> bitumen-seep-rock
    • rare-earth-bolide-> rare-earth-rock
    • geothermal-crack -> geothermal-crack-rock
    • volcanic-pipe -> volcanic-pipe-rock
  • Unify all resource patches to be named <resource>-ore
    • ore-zinc -> zinc ore
    • ore-lead -> lead-ore
    • raw-coal -> raw-coal-ore
    • ore-titanium -> titanium-ore
    • ore-quartz -> quartz-ore
    • ore-nickel -> nickel-ore
    • borax -> borax-ore
    • niobium -> niobium-ore
    • ore-chromium -> chromium-ore
    • oil-sand -> oil-sands-ore
  • ❗ Split up item.lua files by each item's subgroup. (might need to clean up subgroups first)
  • Clean up subgroups
    • I want to do it like this or some other better method, I am very open to suggestions.
  • Reduce all warnings to zero than make it error instead of just warn.
  • Rename dirty-water-light -> muddy-sludge
  • Rename nmf-mk0x -> nanomaterial-factory-mk0x
    • Rename nmf to nanomaterial-factory as well.
  • Scrondrix -> scrondrix
  • Move turd icons into pyalienlife instead of pycoalprocessing
  • Moving some library code from pycoalprocessing and other lower dependencies to pypostprocessing
  • Normalize the -farm and -habitat suffix internally
  • Normalize mk01-mk04 items to always be thing-mk0x internally
  • Turds more extensible
    • Pick a new turd outside of alien life
    • Create new turds outside of alien life
  • Testing code in pypostprocessing/tests/ reworks
    • Write the code in stages to be able to do multi-stage tests
    • Add tests for things that often break (suggestions needed)

Metadata

Metadata

Assignees

No one assigned

    Labels

    WIPIt's being worked onenhancementNew feature or requestminorThe universe is safe... for now.placeholderThis issue is not an issue

    Type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions