-
Notifications
You must be signed in to change notification settings - Fork 57
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
Using a / in a Goal name #240
Comments
The problem is that, when retrieving stored goals (and any other object), the object name is included in the API call, i.e. /api/goals/name/goalname. Consequently, adding the / (even when encoded) leads to a different API path. I've updated the UI to forbid the addition of 'reserved characters' to object names. I've also updated the documentation to indicate this: https://cairis.readthedocs.io/en/latest/reserved.html |
Excellent- Thank you
…On Tue, 1 May 2018, 22:25 Shamal Faily, ***@***.***> wrote:
The problem is that, when retrieving stored goals (and any other object),
the object name is included in the API call, i.e. /api/goals/name/goalname.
Consequently, adding the / (even when encoded) leads to a different API
path.
I've updated the UI to forbid the addition of 'reserved characters' to
object names. I've reflected this in the documentation:
https://cairis.readthedocs.io/en/latest/reserved.html
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#240 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AJ2Fvl_tdMTsiptZBz03xs8dQlsdJwQDks5tuNKtgaJpZM4TtXiU>
.
|
Expected ? Actualbehaviour
Having used a / in a Goal name, when I go to the list of goals and select this example to edit it, the next information screen does not generate/open as expected. Selecting any other Goal continues to work as expected. No error appears in the terminal though.
Steps to reproduce the behaviour
Version of CAIRIS
Current
Operating Systems / Hardware
Win7 - VMw - Linux Ub17 - Chrome
The text was updated successfully, but these errors were encountered: