{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":775604491,"defaultBranch":"main","name":"view_component","ownerLogin":"neanias","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2024-03-21T17:39:22.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/5786847?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1711480605.0","currentOid":""},"activityList":{"items":[{"before":"340a594d91874af8d5788d90d4b3a857693a2964","after":null,"ref":"refs/heads/patch-1","pushedAt":"2024-03-26T19:16:45.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"neanias","name":"William Mathewson","path":"/neanias","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5786847?s=80&v=4"}},{"before":"2f9de9159234add7c21de8bb7e97ed314d74c11a","after":"340a594d91874af8d5788d90d4b3a857693a2964","ref":"refs/heads/patch-1","pushedAt":"2024-03-26T17:54:16.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"joelhawksley","name":"Joel Hawksley","path":"/joelhawksley","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1940294?s=80&v=4"},"commit":{"message":"Apply suggestions from code review","shortMessageHtmlLink":"Apply suggestions from code review"}},{"before":"484a8fda40b27c63c78b7a9ba7bb6360d162cd9d","after":"2f9de9159234add7c21de8bb7e97ed314d74c11a","ref":"refs/heads/patch-1","pushedAt":"2024-03-26T17:51:36.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"joelhawksley","name":"Joel Hawksley","path":"/joelhawksley","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1940294?s=80&v=4"},"commit":{"message":"Update docs/CHANGELOG.md\n\nCo-authored-by: William Mathewson <neanias@users.noreply.github.com>","shortMessageHtmlLink":"Update docs/CHANGELOG.md"}},{"before":"2ac602f566e5c61696c8d374c6275897083ddcd8","after":"484a8fda40b27c63c78b7a9ba7bb6360d162cd9d","ref":"refs/heads/patch-1","pushedAt":"2024-03-26T17:36:12.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"joelhawksley","name":"Joel Hawksley","path":"/joelhawksley","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1940294?s=80&v=4"},"commit":{"message":"Update CHANGELOG.md","shortMessageHtmlLink":"Update CHANGELOG.md"}},{"before":"e5024d73c7594eee810d720a5b43148c376b2e5f","after":"2ac602f566e5c61696c8d374c6275897083ddcd8","ref":"refs/heads/patch-1","pushedAt":"2024-03-26T17:35:22.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"joelhawksley","name":"Joel Hawksley","path":"/joelhawksley","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1940294?s=80&v=4"},"commit":{"message":"Update CHANGELOG.md","shortMessageHtmlLink":"Update CHANGELOG.md"}},{"before":"2380c277cc3deb4737449185a6b196d56932fa42","after":"e5024d73c7594eee810d720a5b43148c376b2e5f","ref":"refs/heads/patch-1","pushedAt":"2024-03-26T17:34:53.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"joelhawksley","name":"Joel Hawksley","path":"/joelhawksley","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1940294?s=80&v=4"},"commit":{"message":"Update docs/CHANGELOG.md","shortMessageHtmlLink":"Update docs/CHANGELOG.md"}},{"before":"095107c8a161f4b27d749a58e208a62aa23ee0b7","after":"2380c277cc3deb4737449185a6b196d56932fa42","ref":"refs/heads/patch-1","pushedAt":"2024-03-22T16:27:25.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"neanias","name":"William Mathewson","path":"/neanias","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5786847?s=80&v=4"},"commit":{"message":"Use component path for generating RSpec files\n\nGenerally, the path to an RSpec file should match the app path, but\nsubstituting `app` for `spec`. If a user changes the generation path for\ntheir components, then the generator should use an appropriate path that\nmatches that. In the example where the user changes the generation path\nfrom `app/components` to `app/views/components`, the RSpec component\nspec should be created in `spec/views/components`.\n\nThe logic chosen here checks that the component is still being generated\ninto the `app` dir, otherwise it will just fallback on the usual\ndestination of `spec/components`.\n\nSince this is a breaking change, it is managed by the\n`use_component_path_for_rspec_tests` config option.\n\nNB: Since this includes the `AbstractGenerator`, we can remove the\n`file_name` method as it's provided by the module.","shortMessageHtmlLink":"Use component path for generating RSpec files"}},{"before":"ba890a7a21f243564d4966f613128dbc44d98361","after":"095107c8a161f4b27d749a58e208a62aa23ee0b7","ref":"refs/heads/patch-1","pushedAt":"2024-03-22T16:19:02.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"neanias","name":"William Mathewson","path":"/neanias","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5786847?s=80&v=4"},"commit":{"message":"Use component path for generating RSpec files\n\nGenerally, the path to an RSpec file should match the app path, but\nsubstituting `app` for `spec`. If a user changes the generation path for\ntheir components, then the generator should use an appropriate path that\nmatches that. In the example where the user changes the generation path\nfrom `app/components` to `app/views/components`, the RSpec component\nspec should be created in `spec/views/components`.\n\nThe logic chosen here checks that the component is still being generated\ninto the `app` dir, otherwise it will just fallback on the usual\ndestination of `spec/components`.\n\nSince this is a breaking change, it is managed by the\n`use_component_path_for_rspec_tests` config option.\n\nNB: Since this includes the `AbstractGenerator`, we can remove the\n`file_name` method as it's provided by the module.","shortMessageHtmlLink":"Use component path for generating RSpec files"}},{"before":"57fc220f0d40c7e5674b8ff4e7e0fac5efefe719","after":"ba890a7a21f243564d4966f613128dbc44d98361","ref":"refs/heads/patch-1","pushedAt":"2024-03-22T15:56:37.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"neanias","name":"William Mathewson","path":"/neanias","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5786847?s=80&v=4"},"commit":{"message":"Use component path for generating RSpec files\n\nGenerally, the path to an RSpec file should match the app path, but\nsubstituting `app` for `spec`. If a user changes the generation path for\ntheir components, then the generator should use an appropriate path that\nmatches that. In the example where the user changes the generation path\nfrom `app/components` to `app/views/components`, the RSpec component\nspec should be created in `spec/views/components`.\n\nThe logic chosen here checks that the component is still being generated\ninto the `app` dir, otherwise it will just fallback on the usual\ndestination of `spec/components`.\n\nSince this is a breaking change, it is managed by the\n`use_component_path_for_rspec_tests` config option.\n\nNB: Since this includes the `AbstractGenerator`, we can remove the\n`file_name` method as it's provided by the module.","shortMessageHtmlLink":"Use component path for generating RSpec files"}},{"before":"278bb41052c6cc2ddc45397554435371cf5da226","after":"57fc220f0d40c7e5674b8ff4e7e0fac5efefe719","ref":"refs/heads/patch-1","pushedAt":"2024-03-22T15:31:28.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"neanias","name":"William Mathewson","path":"/neanias","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5786847?s=80&v=4"},"commit":{"message":"Use component path for generating RSpec files\n\nGenerally, the path to an RSpec file should match the app path, but\nsubstituting `app` for `spec`. If a user changes the generation path for\ntheir components, then the generator should use an appropriate path that\nmatches that. In the example where the user changes the generation path\nfrom `app/components` to `app/views/components`, the RSpec component\nspec should be created in `spec/views/components`.\n\nThe logic chosen here checks that the component is still being generated\ninto the `app` dir, otherwise it will just fallback on the usual\ndestination of `spec/components`.\n\nSince this is a breaking change, it is managed by the\n`use_component_path_for_rspec_tests` config option.\n\nNB: Since this includes the `AbstractGenerator`, we can remove the\n`file_name` method as it's provided by the module.","shortMessageHtmlLink":"Use component path for generating RSpec files"}},{"before":"590df8e1b5fcc19d0a7d8e8b8718507250174c67","after":"278bb41052c6cc2ddc45397554435371cf5da226","ref":"refs/heads/patch-1","pushedAt":"2024-03-22T15:13:53.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"neanias","name":"William Mathewson","path":"/neanias","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5786847?s=80&v=4"},"commit":{"message":"Use component path for generating RSpec files\n\nGenerally, the path to an RSpec file should match the app path, but\nsubstituting `app` for `spec`. If a user changes the generation path for\ntheir components, then the generator should use an appropriate path that\nmatches that. In the example where the user changes the generation path\nfrom `app/components` to `app/views/components`, the RSpec component\nspec should be created in `spec/views/components`.\n\nThe logic chosen here checks that the component is still being generated\ninto the `app` dir, otherwise it will just fallback on the usual\ndestination of `spec/components`.\n\nNB: Since this includes the `AbstractGenerator`, we can remove the\n`file_name` method as it's provided by the module.","shortMessageHtmlLink":"Use component path for generating RSpec files"}},{"before":"8342e18039c05a43d6eeaaa855dd206ea545020c","after":"590df8e1b5fcc19d0a7d8e8b8718507250174c67","ref":"refs/heads/patch-1","pushedAt":"2024-03-22T11:38:03.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"neanias","name":"William Mathewson","path":"/neanias","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5786847?s=80&v=4"},"commit":{"message":"Use component path for generating RSpec files\n\nGenerally, the path to an RSpec file should match the app path, but\nsubstituting `app` for `spec`. If a user changes the generation path for\ntheir components, then the generator should use an appropriate path that\nmatches that. In the example where the user changes the generation path\nfrom `app/components` to `app/views/components`, the RSpec component\nspec should be created in `spec/views/components`.\n\nThe logic chosen here checks that the component is still being generated\ninto the `app` dir, otherwise it will just fallback on the usual\ndestination of `spec/components`.\n\nNB: Since this includes the `AbstractGenerator`, we can remove the\n`file_name` method as it's provided by the module.","shortMessageHtmlLink":"Use component path for generating RSpec files"}},{"before":"49260e922442dba4d23059984b58115c859b29b2","after":"8342e18039c05a43d6eeaaa855dd206ea545020c","ref":"refs/heads/patch-1","pushedAt":"2024-03-21T18:22:26.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"neanias","name":"William Mathewson","path":"/neanias","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5786847?s=80&v=4"},"commit":{"message":"Use component path for generating RSpec files\n\nGenerally, the path to an RSpec file should match the app path, but\nsubstituting `app` for `spec`. If a user changes the generation path for\ntheir components, then the generator should use an appropriate path that\nmatches that. In the example where the user changes the generation path\nfrom `app/components` to `app/views/components`, the RSpec component\nspec should be created in `spec/views/components`.\n\nThe logic chosen here checks that the component is still being generated\ninto the `app` dir, otherwise it will just fallback on the usual\ndestination of `spec/components`.\n\nNB: Since this includes the `AbstractGenerator`, we can remove the\n`file_name` method as it's provided by the module.","shortMessageHtmlLink":"Use component path for generating RSpec files"}},{"before":"5ae3c12e65628bf1d94d222737b0fd8ec0523b5d","after":"49260e922442dba4d23059984b58115c859b29b2","ref":"refs/heads/patch-1","pushedAt":"2024-03-21T18:05:52.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"neanias","name":"William Mathewson","path":"/neanias","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/5786847?s=80&v=4"},"commit":{"message":"Use component path for generating RSpec files\n\nGenerally, the path to an RSpec file should match the app path, but\r\nsubstituting `app` for `spec`. If a user changes the generation path for\r\ntheir components, then the generator should use an appropriate path that\r\nmatches that. In the example where the user changes the generation path\r\nfrom `app/components` to `app/views/components`, the RSpec component\r\nspec should be created in `spec/views/components`.\r\n\r\nThe logic chosen here checks that the component is still being generated\r\ninto the `app` dir, otherwise it will just fallback on the usual\r\ndestination of `spec/components`.\r\n\r\nNB: Since this includes the `AbstractGenerator`, we can remove the\r\n`file_name` method as it's provided by the module.","shortMessageHtmlLink":"Use component path for generating RSpec files"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEH_9E1AA","startCursor":null,"endCursor":null}},"title":"Activity · neanias/view_component"}