Open timalces opened 2 years ago
Currently we pass the project name as a regular parameter, e.g /costs-breakdown/?project=testing. It would be better practice & look cleaner to make it a route parameter, e.g. /testing/costs-breakdown and /testing/events/new
/costs-breakdown/?project=testing
/testing/costs-breakdown
/testing/events/new
By default rails expects the routing param to be the record database id, so this will require some handling to use project name instead. E.g. using https://guides.rubyonrails.org/v6.0/routing.html#overriding-named-route-parameters
Currently we pass the project name as a regular parameter, e.g
/costs-breakdown/?project=testing. It would be better practice & look cleaner to make it a route parameter, e.g./testing/costs-breakdownand/testing/events/newBy default rails expects the routing param to be the record database id, so this will require some handling to use project name instead. E.g. using https://guides.rubyonrails.org/v6.0/routing.html#overriding-named-route-parameters