Support marking module as deprecated #118
Merged
Conversation
This file contains hidden or 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
Member
|
@knolleary - Is it possible for the deprecation details to include a link to a replacement ? |
Member
Author
|
It is sanitised for now. Didn't want it to be a vector for injecting content into the editor. |
Member
|
ok - just have to use words then :-) |
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.
Closes #117
Adds support for deprecating modules in the catalogue - as well as picking that status up from npm.
Admin users now have an option to edit deprecation settings:
Text message is optional.
If deprecated, the message is shown:
It will also pick this up from the npm registry if a module is marked as deprecated then updated - but the admin can override the setting via this ui.
The generated catalogue will then include the
deprecatedproperty as well. Support for reflecting that in the editor will come in 4.1 via node-red/node-red#5134