feat: dynamically cycle ESO, holdfast bounties, hex bounties, & circuit choices #643
@ -43,7 +43,7 @@ export const worldStateController: RequestHandler = (req, res) => {
|
||||
|
|
||||
Nodes: []
|
||||
});
|
||||
|
||||
// Circuit warframe choices cycling every week
|
||||
🛠️ Refactor suggestion Externalize or document large choice arrays The logic for “EXC_NORMAL” and “EXC_HARD” is sound, but the large hardcoded arrays can be difficult to manage or update later. Consider externalizing them into a config file or module for easier maintenance. _:hammer_and_wrench: Refactor suggestion_
**Externalize or document large choice arrays**
The logic for “EXC_NORMAL” and “EXC_HARD” is sound, but the large hardcoded arrays can be difficult to manage or update later. Consider externalizing them into a config file or module for easier maintenance.
<!-- This is an auto-generated comment by CodeRabbit -->
|
||||
// Circuit choices cycling every week
|
||||
|
🛠️ Refactor suggestion Externalize or document large choice arrays The logic for “EXC_NORMAL” and “EXC_HARD” is sound, but the large hardcoded arrays can be difficult to manage or update later. Consider externalizing them into a config file or module for easier maintenance. _:hammer_and_wrench: Refactor suggestion_
**Externalize or document large choice arrays**
The logic for “EXC_NORMAL” and “EXC_HARD” is sound, but the large hardcoded arrays can be difficult to manage or update later. Consider externalizing them into a config file or module for easier maintenance.
<!-- This is an auto-generated comment by CodeRabbit -->
|
||||
worldState.EndlessXpChoices.push({
|
||||
Category: "EXC_NORMAL",
|
||||
Choices: [
|
||||
|
||||
|
🛠️ Refactor suggestion Externalize or document large choice arrays The logic for “EXC_NORMAL” and “EXC_HARD” is sound, but the large hardcoded arrays can be difficult to manage or update later. Consider externalizing them into a config file or module for easier maintenance. _:hammer_and_wrench: Refactor suggestion_
**Externalize or document large choice arrays**
The logic for “EXC_NORMAL” and “EXC_HARD” is sound, but the large hardcoded arrays can be difficult to manage or update later. Consider externalizing them into a config file or module for easier maintenance.
<!-- This is an auto-generated comment by CodeRabbit -->
🛠️ Refactor suggestion Externalize or document large choice arrays The logic for “EXC_NORMAL” and “EXC_HARD” is sound, but the large hardcoded arrays can be difficult to manage or update later. Consider externalizing them into a config file or module for easier maintenance. _:hammer_and_wrench: Refactor suggestion_
**Externalize or document large choice arrays**
The logic for “EXC_NORMAL” and “EXC_HARD” is sound, but the large hardcoded arrays can be difficult to manage or update later. Consider externalizing them into a config file or module for easier maintenance.
<!-- This is an auto-generated comment by CodeRabbit -->
|
||||
🛠️ Refactor suggestion
Externalize or document large choice arrays
The logic for “EXC_NORMAL” and “EXC_HARD” is sound, but the large hardcoded arrays can be difficult to manage or update later. Consider externalizing them into a config file or module for easier maintenance.
🛠️ Refactor suggestion
Externalize or document large choice arrays
The logic for “EXC_NORMAL” and “EXC_HARD” is sound, but the large hardcoded arrays can be difficult to manage or update later. Consider externalizing them into a config file or module for easier maintenance.