-
Notifications
You must be signed in to change notification settings - Fork 8
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
Model Copy: prior to implementing a model copy, allow curators to update the title and then save #490
Comments
Just a side note as we're going through a security audit right now: remember to sanitize your inputs. |
I'll need some more info on this one @kltm :-) |
@vanaukenk Just a note for developers to remember to make sure that the inputs are safe; standard software development practices. |
@kltm @vanaukenk I don't understand why on this ticket though and why now? We are using forms and input everywhere, any specific problem? The sanitization issue should be handled by server Barista or Minerva rather than relying on frontend. I can just paste the evil code in the address bar. All it is doing is send url model copy with new title. But to answer the question, the modern frameworks takes care of sanitization automatically with good coding by interpolation, so no worries. You can check by adding <script>alert("noctua attacked")</script> to any of the new workbenches input |
This feels like a client-side issue. Is there anything for Minerva to do here? |
@tmushayahama - can you elaborate on what the minerva work would be? Thx. |
@vanaukenk @balhoff so ideally it should be minerva. So instead of saving the title as |
I think it would depend on the exact workflow for users, but having this built into the API call for the server would give us more flexibility to try different things and make client programming easier, especially as we're still using different frameworks.
As opposed to a proposed:
As a client developer given how annoying multiple API shots in a safe series in JS can be, the latter looks a lot nicer. This is predicated, naturally, on some assumptions I have on the desired workflow that may not be true. |
@tmushayahama @kltm thanks, that sounds good and should be doable. |
@tmushayahama @balhoff |
@vanaukenk I should be able to add the parameter to accept a title. I need to work on this this week. |
@tmushayahama this is now implemented as part of #482. (2ea2c87). It's also merged into the |
@tmushayahama I forgot to say: the arg is called |
noctua-dev now updated with the latest |
@tmushayahama @kltm I've updated the service to accept the title for the copied model using the same format Noctua has been using when a title is added to an existing model. Basically:
This change is in the PR and has been merged into |
From @tmushayahama (on slack), will hold off on minerva update on noctua-dev until given the word. |
@tmushayahama
|
We'll do the work for 1 above, adding more text to the title of the pop-up window. For 2, we don't have a great all-around solution, so we won't do anything right now and wait for more feedback from curators. |
Curators would like to be able to provide a title to the new model when copying.
UI work will be implemented separately.
From 2022-06-09 workbenches call.
The text was updated successfully, but these errors were encountered: