Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

What is a "lagacy" module and how to avoid or determine the difference #1169

Closed
E3V3A opened this issue Feb 3, 2018 · 1 comment
Closed

What is a "lagacy" module and how to avoid or determine the difference #1169

E3V3A opened this issue Feb 3, 2018 · 1 comment

Comments

@E3V3A
Copy link
Contributor

E3V3A commented Feb 3, 2018

The wiki page for Legacy Modules contain a long list of pretty much most modules. But there is not a word on what makes a module legacy or not. So since nobody in the world of programming likes the word "legacy", I think we need a clear definition what it means here.

  • How to determine if a module is legacy?
  • How to avoid writing new legacy modules?
  • How to update and modify a legacy module, to non-legacy status.

Please consider adding these answers to the very short list of FAQ's...
@MichMich
Copy link
Collaborator

MichMich commented Feb 3, 2018

Those are not Legacy modules. It's a Legacy list, since there is a new grouped list.
The API did not yet have an API change that killed old modules. So there are no legacy modules.

Feel free to edit the Wiki to make this more clear. Thanks.

@MichMich MichMich closed this as completed Feb 3, 2018
@snyk-bot snyk-bot mentioned this issue Jan 18, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@E3V3A @MichMich