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

We should use enum to represent collection type #210

Closed
rossmills99 opened this issue Mar 6, 2020 · 0 comments
Closed

We should use enum to represent collection type #210

rossmills99 opened this issue Mar 6, 2020 · 0 comments
Assignees
@tjoubert

Comments

@rossmills99
Copy link
Collaborator

Collection type is given by 2 = Document, 3 = Edge. This naturally would be represented as an enum type rather than expecting clients to remember the right integer to use
@DiscoPYF DiscoPYF mentioned this issue Apr 19, 2020
Closed
rossmills99 pushed a commit to rossmills99/arangodb-net-standard that referenced this issue Dec 16, 2020
Change collection Type property from integer to enum value.
0a1927f 
Improvement ArangoDB-Community#210
@rossmills99 rossmills99 mentioned this issue Dec 16, 2020
Merged
rossmills99 added a commit that referenced this issue Dec 17, 2020
@rossmills99
Change collection Type property from integer to enum value. (#309)
7e37cab 
* Change collection `Type` property from integer to enum value.

Improvement #210

* Remove redundant setting of camelcase option in string enum conversion.

Co-authored-by: Ross Mills <rmills@actify.com>
@tjoubert tjoubert self-assigned this Jun 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tjoubert tjoubert

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rossmills99 @tjoubert