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.
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
[DFC Orders] List products to import on screen #13125
base: master
Are you sure you want to change the base?
[DFC Orders] List products to import on screen #13125
Changes from 4 commits
8acefed
c3b23a9
447ff3c
9f70000
4624d49
71782de
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see the temptation to call the action import but I would prefer to go with Rails defaults, convention over configuration. In this domain, I would say that we
create
a Product Import. Following that logic, the index action should probably be anew
action. 🤔 But the form on the product import screen could also be seen the thenew
form.What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't think a lot about it, but thought that Rails' resource/collection model didn't fit well in this case, so simply opted to copy the existing action name on the
ProductImportController
.I suppose another way to look at it is an action on the products resource itself, ie:
/admin/products/import
or/admin/products/batch_create
.Ultimately I don't think it's worth thinking about anymore ;)
But it would be good to have a third opinion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To further clarify my thinking, I didn't think there was much "cost" at all using a non-standard action name.
And I think to "create a Product Import" sounds too abstract, which makes it harder to see what it's for.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When possible I prefer to stick with the defaults Rails action, but I think in this case David's solution is acceptable. After all, we can't really refer to Updating or Deleting a "Product Import", we don't have a tangible model for "Product Import".