{"action":"created","issue":{"url":"https://api.github.com/repos/IsraelOrtuno/permalink/issues/12","repository_url":"https://api.github.com/repos/IsraelOrtuno/permalink","labels_url":"https://api.github.com/repos/IsraelOrtuno/permalink/issues/12/labels{/name}","comments_url":"https://api.github.com/repos/IsraelOrtuno/permalink/issues/12/comments","events_url":"https://api.github.com/repos/IsraelOrtuno/permalink/issues/12/events","html_url":"https://github.com/IsraelOrtuno/permalink/issues/12","id":366426169,"node_id":"MDU6SXNzdWUzNjY0MjYxNjk=","number":12,"title":"Feature Idea - Permalink specific route name aliases","user":{"login":"eddielee394","id":7989605,"node_id":"MDQ6VXNlcjc5ODk2MDU=","avatar_url":"https://avatars3.githubusercontent.com/u/7989605?v=4","gravatar_id":"","url":"https://api.github.com/users/eddielee394","html_url":"https://github.com/eddielee394","followers_url":"https://api.github.com/users/eddielee394/followers","following_url":"https://api.github.com/users/eddielee394/following{/other_user}","gists_url":"https://api.github.com/users/eddielee394/gists{/gist_id}","starred_url":"https://api.github.com/users/eddielee394/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eddielee394/subscriptions","organizations_url":"https://api.github.com/users/eddielee394/orgs","repos_url":"https://api.github.com/users/eddielee394/repos","events_url":"https://api.github.com/users/eddielee394/events{/privacy}","received_events_url":"https://api.github.com/users/eddielee394/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-10-03T16:35:09Z","updated_at":"2018-10-04T17:44:48Z","closed_at":null,"author_association":"NONE","body":"What would you think about the ability to add a route name alias to an individual record without requiring  an explicit declaration of the entity Id? This would be useful in development workflows where the database entries aren't always going to be in sync from environment to environment.  \r\nFor example, I encountered an issue where I was using the permalink route name to reference a specific page (i.e. `route(permalink.42)`) on a local environment.  This creates an issue if that id value doesn't exist in the other environment databases.   Even if we created a seed file for modifications made to the permalinks table to ensure it's kept up to date across all env's, the issue then would be potential conflicts with the changes made to the table's current index (id in this case).  Not to mention, generally speaking that would just add another step to the development workflow.\r\n  \r\nI initially considered three workarounds to deal with the issue currently:  \r\n1.  explicitly reference the slug with:  `url('my-permalink-parent', 'my-permalink-child')` in the view; \r\n2.   Query the page object by slug within the controller and then passing the object as variable to the view where i could use the default `$page->route` method.  \r\n3. Use an alias/action map.  \r\n\r\nThe first two workarounds were not really ideal as they used the hard-coded page slugs as primary point of reference - which means if the slug changes, we'd return an error.  If we needed to modify the reference in any way, it would require us to go back and modify the code which isn't very scalable and gets cumbersome when dealing with constantly having to go through build & deployment pipelines, etc.   \r\nThe third workaround would require a unique action for the referenced entry, which i think defeats the purpose of the dynamic nature of the package.  \r\n\r\nSo i was thinking it might smooth things out if we could assign a route name to an individual record, so in these instances we could just use something like:  `route('permalink.my_permalink_child')`.   Then we'd only have to make sure that route name exists in the Permalink table for it's respective entry, regardless of what that entry's id value happens to be.\r\n\r\nMaybe it can be included in the \"custom name column\" idea mentioned in https://github.com/IsraelOrtuno/permalink/issues/5 \r\nWhat do you think?  "},"comment":{"url":"https://api.github.com/repos/IsraelOrtuno/permalink/issues/comments/427108644","html_url":"https://github.com/IsraelOrtuno/permalink/issues/12#issuecomment-427108644","issue_url":"https://api.github.com/repos/IsraelOrtuno/permalink/issues/12","id":427108644,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNzEwODY0NA==","user":{"login":"IsraelOrtuno","id":1769417,"node_id":"MDQ6VXNlcjE3Njk0MTc=","avatar_url":"https://avatars1.githubusercontent.com/u/1769417?v=4","gravatar_id":"","url":"https://api.github.com/users/IsraelOrtuno","html_url":"https://github.com/IsraelOrtuno","followers_url":"https://api.github.com/users/IsraelOrtuno/followers","following_url":"https://api.github.com/users/IsraelOrtuno/following{/other_user}","gists_url":"https://api.github.com/users/IsraelOrtuno/gists{/gist_id}","starred_url":"https://api.github.com/users/IsraelOrtuno/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/IsraelOrtuno/subscriptions","organizations_url":"https://api.github.com/users/IsraelOrtuno/orgs","repos_url":"https://api.github.com/users/IsraelOrtuno/repos","events_url":"https://api.github.com/users/IsraelOrtuno/events{/privacy}","received_events_url":"https://api.github.com/users/IsraelOrtuno/received_events","type":"User","site_admin":false},"created_at":"2018-10-04T17:44:48Z","updated_at":"2018-10-04T17:44:48Z","author_association":"OWNER","body":"Will dig into this 👍 "}}
{"actor":{"display_login":"IsraelOrtuno"}}