Add suppress notifications to Near Future mods #2528
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Getting RP-1 through the express install doesn't suppress the RP-1 recommendations though, so I'm not sure why this doesn't appear with express. I anticipate that CKAN has a hard cutoff to the levels of relations it can do? Express->RP-1->NF Mods->CTT is probably one too many. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to https://discord.com/channels/319857228905447436/620690446540341261/1345817564428767343, there is a strange issue where selecting community tree with RP-1 (non-express I think) causes ckan to pick an older version of RP-1 without the community tech tree conflict. This PR removes recommendations from near future mods to prevent community tech tree from being suggested, although this is not a solution to the problem.