-
Notifications
You must be signed in to change notification settings - Fork 6
added rates_table.public_notes
#238
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.
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
base: master
Are you sure you want to change the base?
Conversation
Azdaroth
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@LeonidMorozov Can you update the changelog please?
StoneFrog
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also response needs updating
| id | Integer | Read | Rates Table's id. | ||
| -----------------|---------|------------------------- | ||
| name | String | Read/Write | **Required**. Rates Table's name. (50 characters max) | ||
| public_notes | Text | Read | Rates Table's public notes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should use JSON types only, right? So String rather than Text
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@StoneFrog , I see Type = Text on other entities as well. Are you sure we should use String ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd keep text, it's obvious that text is longer than string, but we can add a section about what our types mean in the doc if you think this needs clarification.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Azdaroth , WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"String" would be more correct, but I think "Text" is more practical, same as Integer vs. Biginteger.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm ok with keeping text but good to explain it. We already have formats section explaining time, decimal and so on.
|
@Azdaroth please dismiss your review, point about changelog is not valid anymore 😉 |
No description provided.