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

Should ValueType be moved to it's own file? #16

Open
NogginBops opened this issue Sep 23, 2016 · 0 comments
Open

Should ValueType be moved to it's own file? #16

NogginBops opened this issue Sep 23, 2016 · 0 comments

Comments

@NogginBops
Copy link
Contributor

At the moment we have the ValueType enum inside of the SKONObject.cs file. Not in the class but in the namespace. Should this be moved to another file or should it be kept inside?
@NogginBops NogginBops changed the title Should ValueType be move to it's own file? Should ValueType be moved to it's own file? Sep 23, 2016
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
1 participant
@NogginBops