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

Audit core and public API structure and node names #439

Open
jmilloy opened this issue Dec 16, 2020 · 0 comments
Open

Audit core and public API structure and node names #439

jmilloy opened this issue Dec 16, 2020 · 0 comments
Assignees
@CFoye-Creare
Labels
backwards-incompatible Issues and pull requests that must wait for the next major release. fixes-and-maintenance
Projects
Priorities

Comments

@jmilloy
Copy link
Collaborator

jmilloy commented Dec 16, 2020

Description
The public and core APIs need to be made consistent. This includes both the module structure and the node names.

For example, currently

  • inconsistent node class names (nouns like Compositor and verbs like Interpolate)
  • inconsistent submodule names (plural interpolators and singular compositor)
@jmilloy jmilloy added fixes-and-maintenance backwards-incompatible Issues and pull requests that must wait for the next major release. labels Dec 16, 2020
@jmilloy jmilloy added this to To do in Priorities via automation Dec 16, 2020
@jmilloy jmilloy mentioned this issue May 28, 2021
Closed
@CFoye-Creare CFoye-Creare mentioned this issue Jan 25, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CFoye-Creare CFoye-Creare

Labels
backwards-incompatible Issues and pull requests that must wait for the next major release. fixes-and-maintenance
Projects
Priorities
  
To do
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jmilloy @CFoye-Creare