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

Think about renaming "public" API methods #3

Open
SpaceK33z opened this issue Aug 14, 2016 · 1 comment
Open

Think about renaming "public" API methods #3

SpaceK33z opened this issue Aug 14, 2016 · 1 comment
Labels
Breaking change

Comments

@SpaceK33z
Copy link
Contributor

SpaceK33z commented Aug 14, 2016 •
edited
Loading

We have quite some semi-public API methods (e.g., _get_objs), that we are often used to show custom data.

We should think about a proper name for them, and make them public;

  • _get_objs
  • _store
  • _parse_filter
@SpaceK33z
Copy link
Contributor Author

  • _get_objs -> transform_objs or transform_models?
  • _store -> store?

@SpaceK33z SpaceK33z modified the milestone: Version 2 Nov 7, 2016
@SpaceK33z SpaceK33z modified the milestone: Version 2 May 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Breaking change
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sjamaan @SpaceK33z