-
Notifications
You must be signed in to change notification settings - Fork 62
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
RFC URL endpoint building #101
Comments
There must exist one key per |
* Changes views.py to use pid_type in the endpoint map instead of the key for the name of the endpoint. (closes inveniosoftware#101) Signed-off-by: Nikos Filippakis <[email protected]>
Hi! What is the status of this issue? In INSPIRE we are trying to move to official |
* NEW Introduces new RECORDS_REST_PID_TYPE_DEFAULT_ENDPOINT config variable, needed in order to know which default endpoint corresponds to which pid_type when building URIs. (closes inveniosoftware#101) Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new RECORDS_REST_PID_TYPE_DEFAULT_ENDPOINT config variable, needed in order to know which default endpoint corresponds to which pid_type when building URIs. (closes inveniosoftware#101) Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new RECORDS_REST_PID_TYPE_DEFAULT_ENDPOINT config variable, needed in order to know which default endpoint corresponds to which pid_type when building URIs. (closes inveniosoftware#101) Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new RECORDS_REST_PID_TYPE_DEFAULT_ENDPOINT config variable, needed in order to know which default endpoint corresponds to which pid_type when building URIs. (closes inveniosoftware#101) Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new get_default_endpoint_for() helper to obtain the default endpoint-prefix to be used to build endpoints for a given `pid_type`. (closes inveniosoftware#101) * NEW Introduces new `default_endpoint_prefix` prefix to explicitly declare which `endpoint-prefix` to use in case of ambiguity. Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new get_default_endpoint_for() helper to obtain the default endpoint-prefix to be used to build endpoints for a given `pid_type`. (closes inveniosoftware#101) * NEW Introduces new `default_endpoint_prefix` prefix to explicitly declare which `endpoint-prefix` to use in case of ambiguity. Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new get_default_endpoint_for() helper to obtain the default endpoint-prefix to be used to build endpoints for a given `pid_type`. (closes inveniosoftware#101) * NEW Introduces new `default_endpoint_prefix` prefix to explicitly declare which `endpoint-prefix` to use in case of ambiguity. Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new get_default_endpoint_for() helper to obtain the default endpoint-prefix to be used to build endpoints for a given `pid_type`. (closes inveniosoftware#101) * NEW Introduces new `default_endpoint_prefix` prefix to explicitly declare which `endpoint-prefix` to use in case of ambiguity. Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new get_default_endpoint_for() helper to obtain the default endpoint-prefix to be used to build endpoints for a given `pid_type`. (closes inveniosoftware#101) * NEW Introduces new `default_endpoint_prefixes` property to explicitly declare which `endpoint-prefix` to use for which `pid_type`. Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new get_default_endpoint_for() helper to obtain the default endpoint-prefix to be used to build endpoints for a given `pid_type`. (closes inveniosoftware#101) * NEW Introduces new `default_endpoint_prefixes` property to explicitly declare which `endpoint-prefix` to use for which `pid_type`. Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new get_default_endpoint_for() helper to obtain the default endpoint-prefix to be used to build endpoints for a given `pid_type`. (closes inveniosoftware#101) * NEW Introduces new `default_endpoint_prefixes` property to explicitly declare which `endpoint-prefix` to use for which `pid_type`. Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new get_default_endpoint_for() helper to obtain the default endpoint-prefix to be used to build endpoints for a given `pid_type`. (closes inveniosoftware#101) * NEW Introduces new `default_endpoint_prefixes` property to explicitly declare which `endpoint-prefix` to use for which `pid_type`. Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new get_default_endpoint_for() helper to obtain the default endpoint-prefix to be used to build endpoints for a given `pid_type`. (closes inveniosoftware#101) * NEW Introduces new `default_endpoint_prefixes` property to explicitly declare which `endpoint-prefix` to use for which `pid_type`. Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new get_default_endpoint_for() helper to obtain the default endpoint-prefix to be used to build endpoints for a given `pid_type`. (closes inveniosoftware#101) * NEW Introduces new `default_endpoint_prefixes` property to explicitly declare which `endpoint-prefix` to use for which `pid_type`. Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new get_default_endpoint_for() helper to obtain the default endpoint-prefix to be used to build endpoints for a given `pid_type`. (closes inveniosoftware#101) * NEW Introduces new `default_endpoint_prefixes` property to explicitly declare which `endpoint-prefix` to use for which `pid_type`. Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new get_default_endpoint_for() helper to obtain the default endpoint-prefix to be used to build endpoints for a given `pid_type`. (closes inveniosoftware#101) * NEW Introduces new `default_endpoint_prefixes` property to explicitly declare which `endpoint-prefix` to use for which `pid_type`. Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new get_default_endpoint_for() helper to obtain the default endpoint-prefix to be used to build endpoints for a given `pid_type`. (closes inveniosoftware#101) * NEW Introduces new `default_endpoint_prefixes` property to explicitly declare which `endpoint-prefix` to use for which `pid_type`. Signed-off-by: Samuele Kaplun <[email protected]>
* NEW Introduces new cached property on extension state called `default_endpoint_prefixes` that maps `pid_type` to an `endpoint-prefix` used to build endpoints. (closes inveniosoftware#101) Reviewed-by: Jiri Kuncar <[email protected]> Signed-off-by: Samuele Kaplun <[email protected]>
There is a specific reason why to construct the url endpoint is used the
key
ofRECORDS_REST_ENDPOINTS
and sometimes thepid_type
?See:
RecordsListOptionsResource.view_name.format(endpoint),
endpoint = '.{0}_item'.format(pid.pid_type)
Can we simplify and use only one way?
Maybe the best solution is to use the
pid_type
everywhere. WDYT? There are some contraindications?ping @jirikuncar @lnielsen @tiborsimko
The text was updated successfully, but these errors were encountered: