Clarify that index names can be a string or an atom #639
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Definitely both work, I've tried it out to make sure. Not having it specified caused some confusion in my team and I think it can help to specify this.
I did change the time spec, as I'm rather sure it also ends up in there as a string.
I'm a bit surprised/confused that the docs default to atom usage as as best I can tell the index is used for instance here:
(Postgres connection)
which ends up converting the atom back to a string:
But yeah, I don't know as well - I was thinking maybe to use name as a string in the docs at least once to show it's possible but maybe that breaks with a desire for uniformity.
As always, thank you all for your wonderful work! 💚