[
https://issues.apache.org/jira/browse/SOLR-18553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132876#comment-18132876
]
Eric Pugh commented on SOLR-18553:
----------------------------------
Thanks for digging into this... We should limit ourselves to V2 apis only,
they are marked "experimental" so we can change them without backcompat issues.
I think we should open up a PR to consolidate on using noun's not adjectives.
We should add that to our apis-v2-conventions doc. This would make David so
happy that we sweep detailed --> details. What other v2's are like this?
IF schemadesigner v2 has /schema-designer/configs, well, we should make that
scheme-designer/configsets.
In v2, we should strive for consistent parameter names, Again, dont' need to
worry about V1. so if we have collName and collectionName, lets use
collectionName. Bonus points for if names line up with similar names in our
CLI ;)
I think, because we are Java folks, we like camelCase right? Maybe if we were
to change that we A) should get consensus on dev list, B) add it to our
conventions for v2 apis, and C) do that as it's own change.
> Review params and path segments for plurality and consistency
> -------------------------------------------------------------
>
> Key: SOLR-18553
> URL: https://issues.apache.org/jira/browse/SOLR-18553
> Project: Solr
> Issue Type: Sub-task
> Components: v2 API
> Reporter: Eric Pugh
> Priority: Major
>
> There has been discussion about naming, such as "detailed" and "details". We
> have places that maybe should be plural.
>
> See what David put together:
> https://github.com/apache/solr/pull/5064#discussion_r4230690636
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
