[DO NOT MERGE] conditionally filter schematic components to galaxy

[cbortz]

⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️

⚠️ ⚠️ ⚠️ This PR is still under construction ⚠️ ⚠️ ⚠️

⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️

---

To Be Done

• Update filter logic to account for NGE galaxies (i.e. galaxyID=-1)
• Update schematic galaxy mismatch to account for NGE galaxies

---

Summary

• if a galaxy is selected, and the schematic's is a base schematic, filter components for relevant base galaxies and the selected galaxy
  • base galaxy ID 0 is non-NGE, relevant IDs: 0, 1337
  • base galaxy ID -1 is NGE, relevant IDs: -1, 1337
  • base galaxy ID 1337 is Jedi (shared), relevant IDs: -1, 1337
• if a galaxy is selected, and the schematic's is not a base schematic, filter components for relevant base galaxies and the schematic's galaxy
  • base galaxy is determined using the schematic's galaxy as the seed for dbShared.getBaseProfs/1
  • dbShared.getBaseProfs/1 was refactored to short-circuit returns when value is -1, 0, or 1337
• (if a galaxy is not selected, no change)
• add a notice when viewing a schematic for a different galaxy (unless base schematic, i.e. galaxy in (-1, 0, 1337))

Screen Shots

Base schematic with custom components on different servers

In this case, we have two different servers ("Other" and "Test Server"). "Other" has a custom component Super Custom Rifle Barrel. "Test Server" has a custom component Very Advanced Blaster Rifle Barrel. Previously, both custom components would always show. Now, they only show when their respective galaxies are selected.

Viewing a custom schematic from a different server

When viewing a custom schematic for a different server than selected, we display a notice above the schematic details, informing the user that not all ingredients may be available on their server. In this case, we always filter components to the schematic's galaxy (as well as where galaxy=0).

[cbortz]

Notes for later.