Skip to content
This repository has been archived by the owner on Sep 19, 2021. It is now read-only.

Moving to the new API #2

Closed
Nelson-Gon opened this issue Nov 8, 2019 · 2 comments
Closed

Moving to the new API #2

Nelson-Gon opened this issue Nov 8, 2019 · 2 comments
Assignees
@Nelson-Gon
Labels
beginner-friendly documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed migration

Comments

@Nelson-Gon
Copy link
Owner

Nelson-Gon commented Nov 8, 2019 •
edited

The current API is nearing end of life[EOL] by March 31,2020. Is there a way to move the package to the new API without rewriting everything from scratch?
@Nelson-Gon Nelson-Gon added documentation Improvements or additions to documentation enhancement New feature or request migration labels Nov 8, 2019
@Nelson-Gon Nelson-Gon self-assigned this Nov 8, 2019
@Nelson-Gon
Copy link
Owner Author

Nelson-Gon commented Nov 8, 2019 •
edited

Suggestions:

  • Keep package as is until EOL
  • Provide new functions that work with the new API
  • Soft deprecate functions towards EOL
  • Defunct and stick with new API

Questions

  • Should the package be renamed referencing the new API?

@Nelson-Gon Nelson-Gon added beginner-friendly help wanted Extra attention is needed labels Nov 10, 2019
@Nelson-Gon
Copy link
Owner Author

Decision was made to move to a new project: https://github.com/Nelson-Gon/rfdc

@Nelson-Gon Nelson-Gon pinned this issue Jan 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Nelson-Gon Nelson-Gon

Labels
beginner-friendly documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed migration
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Nelson-Gon