#disfactory-notification
2022-04-01
2022-04-02
`<https://github.com/Disfactory/SpotDiffFrontend/commit/d9226ce839a3b7558824d3f89c838fe2ce7de0c6|d9226ce8>` - fix: problem of unable auto-scroll to top or bottom of page `<https://github.com/Disfactory/SpotDiffFrontend/commit/f060e6ba0dfe178f05f4d613cc7eb7da3d0775b0|f060e6ba>` - Merge pull request #71 from Disfactory/ui-0402
`<https://github.com/Disfactory/SpotDiffFrontend/commit/d9226ce839a3b7558824d3f89c838fe2ce7de0c6|d9226ce8>` - fix: problem of unable auto-scroll to top or bottom of page `<https://github.com/Disfactory/SpotDiffFrontend/commit/f060e6ba0dfe178f05f4d613cc7eb7da3d0775b0|f060e6ba>` - Merge pull request #71 from Disfactory/ui-0402
2022-04-03
`<https://github.com/Disfactory/SpotDiffFrontend/commit/6d8acd5c1da6f534a62a6f8c87fad2b68efbc21c|6d8acd5c>` - feat(intro): update intro UI to v1.3 `<https://github.com/Disfactory/SpotDiffFrontend/commit/9c63fa064db68fdfd5d935f01efeb6708772e872|9c63fa06>` - feat(tutorial,game): update UI to v1.3 `<https://github.com/Disfactory/SpotDiffFrontend/commit/0b826b40a8810ca3eb895868cabda3fed74deadd|0b826b40>` - feat(game): update UI of v1.3 `<https://github.com/Disfactory/SpotDiffFrontend/commit/ef52c105da46c04e6f24bfe5b41e7b9bdd3c3370|ef52c105>` - Merge pull request #72 from Disfactory/ui-0402
`<https://github.com/Disfactory/SpotDiffFrontend/commit/6d8acd5c1da6f534a62a6f8c87fad2b68efbc21c|6d8acd5c>` - feat(intro): update intro UI to v1.3 `<https://github.com/Disfactory/SpotDiffFrontend/commit/9c63fa064db68fdfd5d935f01efeb6708772e872|9c63fa06>` - feat(tutorial,game): update UI to v1.3 `<https://github.com/Disfactory/SpotDiffFrontend/commit/0b826b40a8810ca3eb895868cabda3fed74deadd|0b826b40>` - feat(game): update UI of v1.3 `<https://github.com/Disfactory/SpotDiffFrontend/commit/ef52c105da46c04e6f24bfe5b41e7b9bdd3c3370|ef52c105>` - Merge pull request #72 from Disfactory/ui-0402
`<https://github.com/Disfactory/SpotDiffFrontend/commit/430dd6cc26e75a99cd9d207130a290df51b88107|430dd6cc>` - fix(tutorial): problem of showing wrong before/after icon `<https://github.com/Disfactory/SpotDiffFrontend/commit/1c5d20f264cc6ae6aa07c1fee6b51673bbd495f5|1c5d20f2>` - Merge pull request #73 from Disfactory/ui-0403
`<https://github.com/Disfactory/SpotDiffFrontend/commit/430dd6cc26e75a99cd9d207130a290df51b88107|430dd6cc>` - fix(tutorial): problem of showing wrong before/after icon `<https://github.com/Disfactory/SpotDiffFrontend/commit/1c5d20f264cc6ae6aa07c1fee6b51673bbd495f5|1c5d20f2>` - Merge pull request #73 from Disfactory/ui-0403
2022-04-04
2022-04-05
2022-04-06
2022-04-07
2022-04-08
*Is your feature request related to a problem? Please describe.* 新增工廠成功然後回到地圖之後，如果該地點點位附近已經有數個新增的民眾回報工廠，使用者會不知道哪個是自己新增的，無法確認自己是否新增成功。 *Describe the solution you'd like* 讓使用者看得出來自己到底是上傳了到哪個PIN → 三天以內（７２小時）有被EDIT過資訊的PIN，上頭加一個「NEW」 <https://user-images.githubusercontent.com/63245687/162288343-91b3b99d-eb7e-4534-8175-b8c098e36d93.png|image> 詳細設計請參考<https://www.figma.com/file/dFuJKpdDcmHNDqdj1011Zo/Disfactory_UI_design_2021?node-id=362%3A3921|Figma檔案>裡的 [Dev Ready 2.1 ＆2.2] 或 [Design System 2.0] *Describe alternatives you've considered* 新增後可打開該新增的詳細資料（像是<https://disfactory.tw/#map=16/120.45146226883/24.096520670294&factoryId=345e908f-fcf9-40d8-aea1-8b9e1143f398|分享工廠時會直接開該工廠的詳細資料一樣>）
*Is your feature request related to a problem? Please describe.* 新增工廠成功然後回到地圖之後，如果該地點點位附近已經有數個新增的民眾回報工廠，使用者會不知道哪個是自己新增的，無法確認自己是否新增成功。 *Describe the solution you'd like* 讓使用者看得出來自己到底是上傳了到哪個PIN → 三天以內（７２小時）有被EDIT過資訊的PIN，上頭加一個「NEW」 <https://user-images.githubusercontent.com/63245687/162288343-91b3b99d-eb7e-4534-8175-b8c098e36d93.png|image> 詳細設計請參考<https://www.figma.com/file/dFuJKpdDcmHNDqdj1011Zo/Disfactory_UI_design_2021?node-id=362%3A3921|Figma檔案>裡的 [Dev Ready 2.1 ＆2.2] 或 [Design System 2.0] *Describe alternatives you've considered* 新增後可打開該新增的bottom sheet（像是<https://disfactory.tw/#map=16/120.45146226883/24.096520670294&factoryId=345e908f-fcf9-40d8-aea1-8b9e1143f398|分享工廠時會直接開該工廠的詳細資料一樣>）
*Is your feature request related to a problem? Please describe.* 新增工廠成功然後回到地圖之後，如果該地點點位附近已經有數個新增的民眾回報工廠，使用者會不知道哪個是自己新增的，無法確認自己是否新增成功。 *Describe the solution you'd like* 讓使用者看得出來自己到底是上傳了到哪個PIN → 三天以內（７２小時）有被EDIT過資訊的PIN，上頭加一個「NEW」 <https://user-images.githubusercontent.com/63245687/162288343-91b3b99d-eb7e-4534-8175-b8c098e36d93.png|image> 詳細設計請參考<https://www.figma.com/file/dFuJKpdDcmHNDqdj1011Zo/Disfactory_UI_design_2021?node-id=362%3A3921|Figma檔案>裡的 [Dev Ready 2.1 ＆2.2] 或 [Design System 2.0] *Describe alternatives you've considered* 新增後可打開該新增的bottom sheet（像是<https://disfactory.tw/#map=16/120.45146226883/24.096520670294&factoryId=345e908f-fcf9-40d8-aea1-8b9e1143f398|分享工廠時會直接開該工廠的詳細資料一樣>）
*Is your feature request related to a problem? Please describe.* 新增工廠成功然後回到地圖之後，如果該地點點位附近已經有數個新增的民眾回報工廠，使用者會不知道哪個是自己新增的，無法確認自己是否新增成功。 *Describe the solution you'd like* 讓使用者看得出來自己到底是上傳了到哪個PIN → 三天以內（７２小時）有被EDIT過資訊的PIN，上頭加一個「NEW」 <https://user-images.githubusercontent.com/63245687/162288343-91b3b99d-eb7e-4534-8175-b8c098e36d93.png|image> 詳細設計請參考<https://www.figma.com/file/dFuJKpdDcmHNDqdj1011Zo/Disfactory_UI_design_2021?node-id=362%3A3921|Figma檔案>裡的 [Dev Ready 2.1 ＆2.2] 或 [Design System 2.0] *Describe alternatives you've considered* 新增後可打開該新增的詳細資料（像是<https://disfactory.tw/#map=16/120.45146226883/24.096520670294&factoryId=345e908f-fcf9-40d8-aea1-8b9e1143f398|分享工廠時會直接開該工廠的詳細資料一樣>）
*Is your feature request related to a problem? Please describe.* 使用者不確定自己到底在看哪一個工廠的詳細資料。 *Describe the solution you'd like* 被選取的PIN在背景多加一層外框，是什麼顏色的PIN那就用什麼顏色的外框，並將所有其他的pin調整為50%透明度。 <https://user-images.githubusercontent.com/63245687/162289740-68f206d3-1f9f-4168-8a84-cbb425adda1f.png|image> 詳細設計請參考<https://www.figma.com/file/dFuJKpdDcmHNDqdj1011Zo/Disfactory_UI_design_2021?node-id=362%3A3921|Figma檔案>裡的 [Dev Ready 2.1 ＆2.2] 或 [Design System 2.0] *Describe alternatives you've considered* 只調整其他PIN的透明度。
*Is your feature request related to a problem? Please describe.* 使用者不確定自己到底在看哪一個工廠的詳細資料。 *Describe the solution you'd like* 讓使用者知道現在正在看哪個PIN → 更改 active pin的外觀（多加一個框） → 淡化 non active pin （50%透明度） <https://user-images.githubusercontent.com/63245687/162289740-68f206d3-1f9f-4168-8a84-cbb425adda1f.png|image> 詳細設計請參考<https://www.figma.com/file/dFuJKpdDcmHNDqdj1011Zo/Disfactory_UI_design_2021?node-id=362%3A3921|Figma檔案>裡的 [Dev Ready 2.1 ＆2.2] 或 [Design System 2.0] *Describe alternatives you've considered* 只調整其他PIN的透明度。
*Is your feature request related to a problem? Please describe.* 使用者不確定自己到底在看哪一個工廠的詳細資料。 *Describe the solution you'd like* 被選取的PIN在背景多加一層外框，是什麼顏色的PIN那就用什麼顏色的外框，並將所有其他的pin調整為50%透明度。 <https://user-images.githubusercontent.com/63245687/162289740-68f206d3-1f9f-4168-8a84-cbb425adda1f.png|image> 詳細設計請參考<https://www.figma.com/file/dFuJKpdDcmHNDqdj1011Zo/Disfactory_UI_design_2021?node-id=362%3A3921|Figma檔案>裡的 [Dev Ready 2.1 ＆2.2] 或 [Design System 2.0] *Describe alternatives you've considered* 只調整其他PIN的透明度。
*Is your feature request related to a problem? Please describe.* 使用者不確定自己到底在看哪一個工廠的詳細資料。 *Describe the solution you'd like* 讓使用者知道現在正在看哪個PIN → 更改 active pin的外觀（多加一個框） → 淡化 non active pin （50%透明度） <https://user-images.githubusercontent.com/63245687/162289740-68f206d3-1f9f-4168-8a84-cbb425adda1f.png|image> 詳細設計請參考<https://www.figma.com/file/dFuJKpdDcmHNDqdj1011Zo/Disfactory_UI_design_2021?node-id=362%3A3921|Figma檔案>裡的 [Dev Ready 2.1 ＆2.2] 或 [Design System 2.0] *Describe alternatives you've considered* 只調整其他PIN的透明度。
*Describe the bug* 點「常見問題」會自動跳轉到landing page的「教學頁面」，而不是「常見問題」 *To Reproduce* Steps to reproduce the behavior: 列出可以重現問題的步驟： 1. 點disfactory.tw裡面的「常見問題」 *Expected behavior* 希望可以直接自動下滑到 <http://about.disfactory.tw|about.disfactory.tw> 的常見問題 *Screenshots* 直接跳到網頁的這個部分 <https://user-images.githubusercontent.com/63245687/162290612-a50d824d-653a-4138-9038-7411bc93dd56.png|image>
*Describe the bug* 點「常見問題」會自動跳轉到landing page的「教學頁面」，而不是「常見問題」 *To Reproduce* Steps to reproduce the behavior: 列出可以重現問題的步驟： 1. 點disfactory.tw裡面的「常見問題」 *Expected behavior* 希望可以直接自動下滑到 <http://about.disfactory.tw|about.disfactory.tw> 的常見問題 *Screenshots* 直接跳到網頁的這個部分 <https://user-images.githubusercontent.com/63245687/162290612-a50d824d-653a-4138-9038-7411bc93dd56.png|image>
*Describe the bug* 點「常見問題」會自動跳轉到landing page的「教學頁面」，而不是「常見問題」 *To Reproduce* Steps to reproduce the behavior: 列出可以重現問題的步驟： 1. 點disfactory.tw裡面的「常見問題」 *Expected behavior* 希望可以直接自動下滑到 <http://about.disfactory.tw|about.disfactory.tw> 的常見問題 *Screenshots* 直接跳到網頁的這個部分 <https://user-images.githubusercontent.com/63245687/162290612-a50d824d-653a-4138-9038-7411bc93dd56.png|image>
*Describe the bug* 點「常見問題」會自動跳轉到landing page的「教學頁面」，而不是「常見問題」 *To Reproduce* Steps to reproduce the behavior: 列出可以重現問題的步驟： 1. 點disfactory.tw裡面的「常見問題」 *Expected behavior* 希望可以直接自動下滑到 <http://about.disfactory.tw|about.disfactory.tw> 的常見問題 *Screenshots* 直接跳到網頁的這個部分 <https://user-images.githubusercontent.com/63245687/162290612-a50d824d-653a-4138-9038-7411bc93dd56.png|image>
`<https://github.com/Disfactory/SpotDiffFrontend/commit/0a453149a4e835abc779d0d673410b2e6fe99c88|0a453149>` - feat(intro, ending): update UI to v1.3 `<https://github.com/Disfactory/SpotDiffFrontend/commit/11d6bb2039d099c6db6b4842d7417d7dc93ec00b|11d6bb20>` - Merge pull request #74 from Disfactory/fix-0408
`<https://github.com/Disfactory/SpotDiffFrontend/commit/0a453149a4e835abc779d0d673410b2e6fe99c88|0a453149>` - feat(intro, ending): update UI to v1.3 `<https://github.com/Disfactory/SpotDiffFrontend/commit/11d6bb2039d099c6db6b4842d7417d7dc93ec00b|11d6bb20>` - Merge pull request #74 from Disfactory/fix-0408
*1. 地址字串處理* 目前在遊戲頁面中，並沒有顯示該圖片的地址。原因在於目前地址可能會顯示「縣市+鄉鎮市區+村里」或是「縣市+鄉鎮市區」，但我們只希望呈現「縣市+鄉鎮市區」。之前也有遇到情形是「台灣省+縣市+鄉鎮市區」，但不確定目前的資料會不會仍遇到這個情形，可能要詢問 <https://github.com/deeper747|@deeper747> 。 具體的code寫在元件<https://github.com/Disfactory/SpotDiffFrontend/blob/main/src/components/GameTaskA.vue#L12|GameTaskA>與<https://github.com/Disfactory/SpotDiffFrontend/blob/main/src/components/GameTaskB.vue#L12|GameTaskB> *2. head裡面加上tag。* 目前該專案並沒有加上meta tag，導致分享時會沒有圖片與說明（如下圖），SEO也不好。 <https://user-images.githubusercontent.com/85677992/162427313-f825198a-d6c7-4ca6-b90e-612d58692947.png|Screen Shot 2022-04-08 at 7 06 37 PM> 可以參考<https://github.com/Disfactory/about.disfactory.tw/blob/dev/nuxt.config.js#L95-L112|about.disfactory.tw>裡面列的meta（注意，about.disfatory.tw是用nuxt寫的，但本專案則只使用vue，兩者設定meta tag的方式可能不同）。meta tag的具體內容，也請詢問 <https://github.com/deeper747|@deeper747>。 *3. 教學地圖載入優化* 目前教學頁面的圖片是一張png圖，而在
*1. 地址字串處理* 目前在遊戲頁面中，並沒有顯示該圖片的地址。原因在於目前地址可能會顯示「縣市+鄉鎮市區+村里」或是「縣市+鄉鎮市區」，但我們只希望呈現「縣市+鄉鎮市區」。之前也有遇到情形是「台灣省+縣市+鄉鎮市區」，但不確定目前的資料會不會仍遇到這個情形，可能要詢問 <https://github.com/deeper747|@deeper747> 。 具體的code寫在元件<https://github.com/Disfactory/SpotDiffFrontend/blob/main/src/components/GameTaskA.vue#L12|GameTaskA>與<https://github.com/Disfactory/SpotDiffFrontend/blob/main/src/components/GameTaskB.vue#L12|GameTaskB> *2. head裡面加上tag。* 目前該專案並沒有加上meta tag，導致分享時會沒有圖片與說明（如下圖），SEO也不好。 <https://user-images.githubusercontent.com/85677992/162427313-f825198a-d6c7-4ca6-b90e-612d58692947.png|Screen Shot 2022-04-08 at 7 06 37 PM> 可以參考<https://github.com/Disfactory/about.disfactory.tw/blob/dev/nuxt.config.js#L95-L112|about.disfactory.tw>裡面列的meta（注意，about.disfatory.tw是用nuxt寫的，但本專案則只使用vue，兩者設定meta tag的方式可能不同）。meta tag的具體內容，也請詢問 <https://github.com/deeper747|@deeper747>。 *3. 教學地圖載入優化* 目前教學頁面的圖片是一張png圖，而在切換題目的時候，會有0.5-1秒的時間，圖片還沒被掛載上去，導致使用者會看到一個空的框框。 像這樣： <https://user-images.githubusercontent.com/85677992/162428490-b1b6ba2b-1705-4fbb-aecb-c61f8b2ec006.png|Screen Shot 2022-04-08 at 7 37 32 PM> 或這樣 <https://user-images.githubusercontent.com/85677992/162428549-5f1f8305-274f-4d91-9797-36bcde1bd8fd.png|Screen Shot 2022-04-08 at 7 38 14 PM> *4. 遊戲頁面衛星雲圖載入優化* 可參考 <https://github.com/Disfactory/SpotDiffFrontend/issues/40|#40>
2022-04-09
*Describe the bug* A clear and concise description of what the bug is. 請清晰詳細的描述這個問題 *To Reproduce* Steps to reproduce the behavior: 列出可以重現問題的步驟： 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error *Expected behavior* A clear and concise description of what you expected to happen. *Screenshots* If applicable, add screenshots to help explain your problem. 截圖 *Desktop (please complete the following information):* • OS: [e.g. iOS] • Browser [e.g. chrome, safari] • Version [e.g. 22] *Smartphone (please complete the following information):* • Device: [e.g. iPhone6] • OS: [e.g. iOS8.1] • Browser [e.g. stock browser, safari] • Version [e.g. 22] *Additional context* Add any other context about the problem here.
*Describe the bug* A clear and concise description of what the bug is. 請清晰詳細的描述這個問題 *To Reproduce* Steps to reproduce the behavior: 列出可以重現問題的步驟： 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error *Expected behavior* A clear and concise description of what you expected to happen. *Screenshots* If applicable, add screenshots to help explain your problem. 截圖 *Desktop (please complete the following information):* • OS: [e.g. iOS] • Browser [e.g. chrome, safari] • Version [e.g. 22] *Smartphone (please complete the following information):* • Device: [e.g. iPhone6] • OS: [e.g. iOS8.1] • Browser [e.g. stock browser, safari] • Version [e.g. 22] *Additional context* Add any other context about the problem here.
*Describe the bug* A clear and concise description of what the bug is. 請清晰詳細的描述這個問題 *To Reproduce* Steps to reproduce the behavior: 列出可以重現問題的步驟： 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error *Expected behavior* A clear and concise description of what you expected to happen. *Screenshots* If applicable, add screenshots to help explain your problem. 截圖 *Desktop (please complete the following information):* • OS: [e.g. iOS] • Browser [e.g. chrome, safari] • Version [e.g. 22] *Smartphone (please complete the following information):* • Device: [e.g. iPhone6] • OS: [e.g. iOS8.1] • Browser [e.g. stock browser, safari] • Version [e.g. 22] *Additional context* Add any other context about the problem here.
*Describe the bug* A clear and concise description of what the bug is. 請清晰詳細的描述這個問題 *To Reproduce* Steps to reproduce the behavior: 列出可以重現問題的步驟： 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error *Expected behavior* A clear and concise description of what you expected to happen. *Screenshots* If applicable, add screenshots to help explain your problem. 截圖 *Desktop (please complete the following information):* • OS: [e.g. iOS] • Browser [e.g. chrome, safari] • Version [e.g. 22] *Smartphone (please complete the following information):* • Device: [e.g. iPhone6] • OS: [e.g. iOS8.1] • Browser [e.g. stock browser, safari] • Version [e.g. 22] *Additional context* Add any other context about the problem here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
adds some extra keys because of newer npm version
adds some extra keys because of newer npm version
adds some extra keys because of newer npm version
adds some extra keys because of newer npm version
`<https://github.com/Disfactory/frontend/commit/10aa31b15b8b3ae0cc548235393b0386d0c143fc|10aa31b1>` - fix npm install on m1, remove unused fiber dependency `<https://github.com/Disfactory/frontend/commit/81f86333a5cc66cb09251f88406967dbf9e33a21|81f86333>` - Merge pull request #151 from bdon/bdon/update-packages-m1
`<https://github.com/Disfactory/frontend/commit/10aa31b15b8b3ae0cc548235393b0386d0c143fc|10aa31b1>` - fix npm install on m1, remove unused fiber dependency `<https://github.com/Disfactory/frontend/commit/81f86333a5cc66cb09251f88406967dbf9e33a21|81f86333>` - Merge pull request #151 from bdon/bdon/update-packages-m1
`<https://github.com/Disfactory/frontend/commit/10aa31b15b8b3ae0cc548235393b0386d0c143fc|10aa31b1>` - fix npm install on m1, remove unused fiber dependency `<https://github.com/Disfactory/frontend/commit/81f86333a5cc66cb09251f88406967dbf9e33a21|81f86333>` - Merge pull request #151 from bdon/bdon/update-packages-m1
`<https://github.com/Disfactory/frontend/commit/10aa31b15b8b3ae0cc548235393b0386d0c143fc|10aa31b1>` - fix npm install on m1, remove unused fiber dependency `<https://github.com/Disfactory/frontend/commit/81f86333a5cc66cb09251f88406967dbf9e33a21|81f86333>` - Merge pull request #151 from bdon/bdon/update-packages-m1
讓 <https://about.disfactory.tw#faq|https://about.disfactory.tw#faq> 可以連
Disables clustering by setting cluster distance to 0 at a certain zoom level. we can adjust the zoom level.
Disables clustering by setting cluster distance to 0 at a certain zoom level. we can adjust the zoom level.
`<https://github.com/Disfactory/frontend/commit/ae7c02280ac6ed3a19e763e727771e474d95a370|ae7c0228>` - Disable clustering at zoom level > 16 [#150] `<https://github.com/Disfactory/frontend/commit/011c59b6ff2ecca8ead146a8f4e2b17d4fb160b7|011c59b6>` - Merge pull request #153 from Disfactory/bdon/disable-clustering-zoom
`<https://github.com/Disfactory/frontend/commit/ae7c02280ac6ed3a19e763e727771e474d95a370|ae7c0228>` - Disable clustering at zoom level > 16 [#150] `<https://github.com/Disfactory/frontend/commit/011c59b6ff2ecca8ead146a8f4e2b17d4fb160b7|011c59b6>` - Merge pull request #153 from Disfactory/bdon/disable-clustering-zoom
`<https://github.com/Disfactory/frontend/commit/ae7c02280ac6ed3a19e763e727771e474d95a370|ae7c0228>` - Disable clustering at zoom level > 16 [#150] `<https://github.com/Disfactory/frontend/commit/011c59b6ff2ecca8ead146a8f4e2b17d4fb160b7|011c59b6>` - Merge pull request #153 from Disfactory/bdon/disable-clustering-zoom
`<https://github.com/Disfactory/frontend/commit/ae7c02280ac6ed3a19e763e727771e474d95a370|ae7c0228>` - Disable clustering at zoom level > 16 [#150] `<https://github.com/Disfactory/frontend/commit/011c59b6ff2ecca8ead146a8f4e2b17d4fb160b7|011c59b6>` - Merge pull request #153 from Disfactory/bdon/disable-clustering-zoom
`<https://github.com/Disfactory/frontend/commit/4326e354c980336129e0f5034d7bda8dacec7ea1|4326e354>` - feat: change protomap url to production `<https://github.com/Disfactory/frontend/commit/54b4bd17dabee83e52b80de0e232cf80f521aa48|54b4bd17>` - Merge pull request #154 from Disfactory/yukai/change-protomaps-url
`<https://github.com/Disfactory/frontend/commit/4326e354c980336129e0f5034d7bda8dacec7ea1|4326e354>` - feat: change protomap url to production `<https://github.com/Disfactory/frontend/commit/54b4bd17dabee83e52b80de0e232cf80f521aa48|54b4bd17>` - Merge pull request #154 from Disfactory/yukai/change-protomaps-url
`<https://github.com/Disfactory/frontend/commit/4326e354c980336129e0f5034d7bda8dacec7ea1|4326e354>` - feat: change protomap url to production `<https://github.com/Disfactory/frontend/commit/54b4bd17dabee83e52b80de0e232cf80f521aa48|54b4bd17>` - Merge pull request #154 from Disfactory/yukai/change-protomaps-url
`<https://github.com/Disfactory/frontend/commit/4326e354c980336129e0f5034d7bda8dacec7ea1|4326e354>` - feat: change protomap url to production `<https://github.com/Disfactory/frontend/commit/54b4bd17dabee83e52b80de0e232cf80f521aa48|54b4bd17>` - Merge pull request #154 from Disfactory/yukai/change-protomaps-url
用行政區,地政事務所代碼,段名,段號,地號作為 identifier。 針對 2018 & 2022 的資料，各有 6000 多筆資料是有重複的 identifier。 應該需要抽樣、手動去檢查一些重複的資訊，否則 disfactory 後端的資料可能會有重複，重複的資料，可能也會讓前端使用者無法單選特定的工廠。
用行政區,地政事務所代碼,段名,段號,地號作為 identifier。 針對 2018 & 2022 的資料，各有 6000 多筆資料是有重複的 identifier。 應該需要抽樣、手動去檢查一些重複的資訊，否則 disfactory 後端的資料可能會有重複，重複的資料，可能也會讓前端使用者無法單選特定的工廠。
`<https://github.com/Disfactory/SpotDiffFrontend/commit/219c6742e3467e56c9858e1517cd871678baa1bc|219c6742>` - feat(game): add address in certain format `<https://github.com/Disfactory/SpotDiffFrontend/commit/cdff5568090793804834759ae940d80f528d571f|cdff5568>` - Merge pull request #77 from Disfactory/fix-address-0409
`<https://github.com/Disfactory/SpotDiffFrontend/commit/219c6742e3467e56c9858e1517cd871678baa1bc|219c6742>` - feat(game): add address in certain format `<https://github.com/Disfactory/SpotDiffFrontend/commit/cdff5568090793804834759ae940d80f528d571f|cdff5568>` - Merge pull request #77 from Disfactory/fix-address-0409
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
2022-04-10
2022-04-11
<https://user-images.githubusercontent.com/8353239/162678220-c4e724a3-b3b6-4fcb-a89f-5df8f154d991.gif|hand>
<https://user-images.githubusercontent.com/8353239/162678220-c4e724a3-b3b6-4fcb-a89f-5df8f154d991.gif|hand>
<https://www.figma.com/file/TVAEC28E3ojabGHc8BawbI/%E5%A4%A7%E5%AE%B6%E4%BE%86%E6%89%BE%E5%BB%A0?node-id=599%3A433|Figma> 需要設計 1. 地公分享的圖片（og:image 與此相同） 2. user 從網站分享出去的圖片 <https://user-images.githubusercontent.com/8353239/162678506-59b0f255-2b96-45b1-8c68-92aa915e5ff2.png|Screen Shot 2022-04-11 at 11 30 15 AM>
<https://user-images.githubusercontent.com/8353239/162678506-59b0f255-2b96-45b1-8c68-92aa915e5ff2.png|Screen Shot 2022-04-11 at 11 30 15 AM>
2022-04-12
2022-04-13
*Is your feature request related to a problem? Please describe.* Displaying `null` makes user confused if they have successfully added a new pin. *Describe the solution you'd like* While waiting for the landcode data from the government's website, the page could display `擷取中` to inform users that the data are coming through. *Additional context* <https://user-images.githubusercontent.com/9480974/163164747-0537a813-471b-4a1f-9d5e-c4d70a2c9688.jpeg|disfactory_landcode_null>
*Is your feature request related to a problem? Please describe.* Displaying `null` makes user confused if they have successfully added a new pin. *Describe the solution you'd like* While waiting for the landcode data from the government's website, the page could display `擷取中` to inform users that the data are coming through. *Additional context* <https://user-images.githubusercontent.com/9480974/163164747-0537a813-471b-4a1f-9d5e-c4d70a2c9688.jpeg|disfactory_landcode_null>
*Is your feature request related to a problem? Please describe.* Displaying `null` makes user confused if they have successfully added a new pin. *Describe the solution you'd like* While waiting for the landcode data from the government's website, the page could display `擷取中` to inform users that the data are coming through. *Additional context* <https://user-images.githubusercontent.com/9480974/163164747-0537a813-471b-4a1f-9d5e-c4d70a2c9688.jpeg|disfactory_landcode_null>
*Is your feature request related to a problem? Please describe.* Displaying `null` makes user confused if they have successfully added a new pin. *Describe the solution you'd like* While waiting for the landcode data from the government's website, the page could display `擷取中` to inform users that the data are coming through. *Additional context* <https://user-images.githubusercontent.com/9480974/163164747-0537a813-471b-4a1f-9d5e-c4d70a2c9688.jpeg|disfactory_landcode_null>
*Expected Behavior* In the first question of a set, the photo is the "before" photo. The tag should be `before` instead `after` *Current Behavior* <https://user-images.githubusercontent.com/9480974/163166095-3dda5af7-1483-4495-b66f-044616cbdb60.png|螢幕快照 2022-04-13 下午6 55 21>
*Expected Behavior* In the first question of a set, the photo is the "before" photo. The tag should be `before` instead `after` *Current Behavior* <https://user-images.githubusercontent.com/9480974/163166095-3dda5af7-1483-4495-b66f-044616cbdb60.png|螢幕快照 2022-04-13 下午6 55 21>
*Expected Behavior* No confusing photo while loading. *Current Behavior* 1. Start the game 2. A satellite image of farmland flashes before the actual image to display. (Every time is the same farmland image) *Problems* Users may accidentally press the `farmland` button because of that image, which will hurt our data quality. *Screenshots* <https://user-images.githubusercontent.com/9480974/163167363-ddfdaa31-1120-4936-9e56-2824039e2da1.jpeg|flashed_farmland_image> *Smartphone (please complete the following information):* • OS: iOS 15.1 • Browser: Safari
*Expected Behavior* No confusing photo while loading. *Current Behavior* 1. Start the game 2. A satellite image of farmland flashes before the actual image to display. (Every time is the same farmland image) *Problems* Users may accidentally press the `farmland` button because of that image, which will hurt our data quality. *Screenshots* <https://user-images.githubusercontent.com/9480974/163167363-ddfdaa31-1120-4936-9e56-2824039e2da1.jpeg|flashed_farmland_image> *Smartphone (please complete the following information):* • OS: iOS 15.1 • Browser: Safari
*Expected Behavior* Three buttons for answers as other questions with a choice of `不知道`(雖然我覺得文字改成 `不清楚` 會比較好) *Current Behavior* Only two choices in the second question of one set: `有擴建` `無擴建` `有建物` `無建物` *Suggested solutions* `有擴建` `無擴建` `不清楚` `有建物` `無建物` `不清楚` *Context (Environment)* We still need a third option to lift user's cognitive burdens and indicate the ambiguity of that coordinate. *Screenshots* <https://user-images.githubusercontent.com/9480974/163168884-c7efb57f-0653-4b8b-8606-c56f007d7dd3.png|螢幕快照 2022-04-13 下午6 55 21> <https://user-images.githubusercontent.com/9480974/163168895-e3294dc7-917a-4f31-8eab-c00d79bfb585.png|螢幕快照 2022-04-13 下午7 16 45>
*Expected Behavior* Three buttons for answers as other questions with a choice of `不知道`(雖然我覺得文字改成 `不清楚` 會比較好) *Current Behavior* Only two choices in the second question of one set: `有擴建` `無擴建` `有建物` `無建物` *Suggested solutions* `有擴建` `無擴建` `不清楚` `有建物` `無建物` `不清楚` *Context (Environment)* We still need a third option to lift user's cognitive burdens and indicate the ambiguity of that coordinate. *Screenshots* <https://user-images.githubusercontent.com/9480974/163168884-c7efb57f-0653-4b8b-8606-c56f007d7dd3.png|螢幕快照 2022-04-13 下午6 55 21> <https://user-images.githubusercontent.com/9480974/163168895-e3294dc7-917a-4f31-8eab-c00d79bfb585.png|螢幕快照 2022-04-13 下午7 16 45>
目前還沒有 before/after 滑動的操作 *Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
目前還沒有 before/after 滑動的操作 *Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
前面都有阿伯動畫，只有最後一頁沒有，好像不夠興奮 XDDDD *Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
前面都有阿伯動畫，只有最後一頁沒有，好像不夠興奮 XDDDD *Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
<https://dev.disfactory.tw/#map=17.27/120.48586940048851/24.087633368347312|https://dev.disfactory.tw/#map=17.27/120.48586940048851/24.087633368347312> <https://user-images.githubusercontent.com/4230968/163190982-7cbe4b9f-4883-44a3-8335-a265bfb5ba0c.png|スクリーンショット 2022-04-13 午後9 26 59>
<https://dev.disfactory.tw/#map=17.27/120.48586940048851/24.087633368347312|https://dev.disfactory.tw/#map=17.27/120.48586940048851/24.087633368347312> <https://user-images.githubusercontent.com/4230968/163190982-7cbe4b9f-4883-44a3-8335-a265bfb5ba0c.png|スクリーンショット 2022-04-13 午後9 26 59>
<https://dev.disfactory.tw/#map=17.27/120.48586940048851/24.087633368347312|https://dev.disfactory.tw/#map=17.27/120.48586940048851/24.087633368347312> <https://user-images.githubusercontent.com/4230968/163190982-7cbe4b9f-4883-44a3-8335-a265bfb5ba0c.png|スクリーンショット 2022-04-13 午後9 26 59>
<https://dev.disfactory.tw/#map=17.27/120.48586940048851/24.087633368347312|https://dev.disfactory.tw/#map=17.27/120.48586940048851/24.087633368347312> <https://user-images.githubusercontent.com/4230968/163190982-7cbe4b9f-4883-44a3-8335-a265bfb5ba0c.png|スクリーンショット 2022-04-13 午後9 26 59>
fixes <https://github.com/Disfactory/frontend/issues/128|#128>
fixes <https://github.com/Disfactory/frontend/issues/128|#128>
fixes <https://github.com/Disfactory/frontend/issues/128|#128>
fixes <https://github.com/Disfactory/frontend/issues/128|#128>
讓 admin 頁面可以用 factory id 搜尋 factory
讓 admin 頁面可以用 factory id 搜尋 factory
2022-04-14
_Problems_ Very few locations are done after > 600 answers. (Location would be marked done only if two answers from qualified users, who passed the gold standard, match. *Reasons* Many answered the first question on landusage with 不知道(0) while the gold standards are always 1 or 2. The gold standards were set not from the current user interface but from Google Earth, which looks different. As the result, some locations look very ambiguous for users to identify whether it was farmland or not, e.g. the aim point was put on a road or on the boundary of farmland and buildings. Nevertheless, the answer to the second question (new building?/New extension of existing building?) are usually quite good as it is easier to identify the changes. Those answers that didn't pass the gold standards are still usable for our research. _Decisions_ • Disable unclear gold standards => `gold_standard_status == 3` 0: gold standard itself 1: pass gold standard 2: fail gold standard 3: disabled gold standard • <https://github.com/deeper747|@deeper747> will give a set of gold standards to be disabled and a new set of gold standards (<https://github.com/dyfu95|@dyfu95> is building another interface for <https://github.com/deeper747|@deeper747> to select the new set of goldstandards) • The data collected during April 9-13 that didn't pass the landusage gold standards (those select 0: unclear instead of 1 or 2 assigned by gold standards) keep `gold_standard_status == 2` (not passing the gold standards). We can identify these data later by timestamps.
_Problems_ Very few locations are done after > 600 answers. (Location would be marked done only if two answers from qualified users, who passed the gold standard, match. *Reasons* Many answered the first question on landusage with 不知道(0) while the gold standards are always 1 or 2. The gold standards were set not from the current user interface but from Google Earth, which looks different. As the result, some locations look very ambiguous for users to identify whether it was farmland or not, e.g. the aim point was put on a road or on the boundary of farmland and buildings. Nevertheless, the answer to the second question (new building?/New extension of existing building?) are usually quite good as it is easier to identify the changes. Those answers that didn't pass the gold standards are still usable for our research. _Decisions_ • Disable unclear gold standards => `gold_standard_status == 3` 0: gold standard itself 1: pass gold standard 2: fail gold standard 3: disabled gold standard • <https://github.com/deeper747|@deeper747> will give a set of gold standards to be disabled and a new set of gold standards (<https://github.com/dyfu95|@dyfu95> is building another interface for <https://github.com/deeper747|@deeper747> to select the new set of goldstandards <https://github.com/Disfactory/SpotDiffFrontend/issues/87|Disfactory/SpotDiffFrontend#87>) • The data collected during April 9-13 that didn't pass the landusage gold standards (those select 0: unclear instead of 1 or 2 assigned by gold standards) keep `gold_standard_status == 2` (not passing the gold standards). We can identify these data later by timestamps.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
*Is your feature request related to a problem? Please describe.* A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] *Describe the solution you'd like* A clear and concise description of what you want to happen. *Describe alternatives you've considered* A clear and concise description of any alternative solutions or features you've considered. *Additional context* Add any other context or screenshots about the feature request here.
2022-04-15
2022-04-16
2022-04-17
2022-04-18
2022-04-19
Add set_answer_gold_standard_status and related test code / utility to delete gold standard by changing gold_standard_status 3.
Add set_answer_gold_standard_status and related test code / utility to delete gold standard by changing gold_standard_status 3.
2022-04-20
`<https://github.com/Disfactory/Disfactory/commit/e333ec69177485bb6e9d8329a2e1455c07593e60|e333ec69>` - user can search factory by factory id `<https://github.com/Disfactory/Disfactory/commit/83d843cf9b54824b11b6e089fff9bc96a4ee14c4|83d843cf>` - Merge pull request #598 from Swind/search_by_factory_id
`<https://github.com/Disfactory/Disfactory/commit/e333ec69177485bb6e9d8329a2e1455c07593e60|e333ec69>` - user can search factory by factory id `<https://github.com/Disfactory/Disfactory/commit/83d843cf9b54824b11b6e089fff9bc96a4ee14c4|83d843cf>` - Merge pull request #598 from Swind/search_by_factory_id
`<https://github.com/Disfactory/frontend/commit/1d31914a697855fe1a03c73bc57a65c384f78301|1d31914a>` - feat: add factory followups to ui `<https://github.com/Disfactory/frontend/commit/5f6a2268a6b3db2360d6334a3d098266c964ad7e|5f6a2268>` - fix: followup format `<https://github.com/Disfactory/frontend/commit/5e712d477339d4775501c2abc940cd296b935244|5e712d47>` - fix: only show followup when there's any `<https://github.com/Disfactory/frontend/commit/845c881443b8a8c661c42c15bb104274290b0a85|845c8814>` - Merge pull request #159 from Disfactory/yukai/128-followup-info
`<https://github.com/Disfactory/frontend/commit/1d31914a697855fe1a03c73bc57a65c384f78301|1d31914a>` - feat: add factory followups to ui `<https://github.com/Disfactory/frontend/commit/5f6a2268a6b3db2360d6334a3d098266c964ad7e|5f6a2268>` - fix: followup format `<https://github.com/Disfactory/frontend/commit/5e712d477339d4775501c2abc940cd296b935244|5e712d47>` - fix: only show followup when there's any `<https://github.com/Disfactory/frontend/commit/845c881443b8a8c661c42c15bb104274290b0a85|845c8814>` - Merge pull request #159 from Disfactory/yukai/128-followup-info
`<https://github.com/Disfactory/frontend/commit/1d31914a697855fe1a03c73bc57a65c384f78301|1d31914a>` - feat: add factory followups to ui `<https://github.com/Disfactory/frontend/commit/5f6a2268a6b3db2360d6334a3d098266c964ad7e|5f6a2268>` - fix: followup format `<https://github.com/Disfactory/frontend/commit/5e712d477339d4775501c2abc940cd296b935244|5e712d47>` - fix: only show followup when there's any `<https://github.com/Disfactory/frontend/commit/845c881443b8a8c661c42c15bb104274290b0a85|845c8814>` - Merge pull request #159 from Disfactory/yukai/128-followup-info
`<https://github.com/Disfactory/frontend/commit/1d31914a697855fe1a03c73bc57a65c384f78301|1d31914a>` - feat: add factory followups to ui `<https://github.com/Disfactory/frontend/commit/5f6a2268a6b3db2360d6334a3d098266c964ad7e|5f6a2268>` - fix: followup format `<https://github.com/Disfactory/frontend/commit/5e712d477339d4775501c2abc940cd296b935244|5e712d47>` - fix: only show followup when there's any `<https://github.com/Disfactory/frontend/commit/845c881443b8a8c661c42c15bb104274290b0a85|845c8814>` - Merge pull request #159 from Disfactory/yukai/128-followup-info
`<https://github.com/Disfactory/frontend/commit/dd94a047a4c8f0d751d7cf4b91b8b4214c58e78d|dd94a047>` - fix: remove followup date `<https://github.com/Disfactory/frontend/commit/6f62f19fb4adb09186e7e9f7279fa95b5a810077|6f62f19f>` - Merge pull request #157 from Disfactory/release/2.5.0 `<https://github.com/Disfactory/frontend/commit/06a154e7fe8d0a335bd59405c4767b1695ce0050|06a154e7>` - Merge remote-tracking branch 'origin/production'
`<https://github.com/Disfactory/frontend/commit/dd94a047a4c8f0d751d7cf4b91b8b4214c58e78d|dd94a047>` - fix: remove followup date `<https://github.com/Disfactory/frontend/commit/6f62f19fb4adb09186e7e9f7279fa95b5a810077|6f62f19f>` - Merge pull request #157 from Disfactory/release/2.5.0 `<https://github.com/Disfactory/frontend/commit/06a154e7fe8d0a335bd59405c4767b1695ce0050|06a154e7>` - Merge remote-tracking branch 'origin/production'
`<https://github.com/Disfactory/frontend/commit/dd94a047a4c8f0d751d7cf4b91b8b4214c58e78d|dd94a047>` - fix: remove followup date `<https://github.com/Disfactory/frontend/commit/6f62f19fb4adb09186e7e9f7279fa95b5a810077|6f62f19f>` - Merge pull request #157 from Disfactory/release/2.5.0 `<https://github.com/Disfactory/frontend/commit/06a154e7fe8d0a335bd59405c4767b1695ce0050|06a154e7>` - Merge remote-tracking branch 'origin/production'
`<https://github.com/Disfactory/frontend/commit/dd94a047a4c8f0d751d7cf4b91b8b4214c58e78d|dd94a047>` - fix: remove followup date `<https://github.com/Disfactory/frontend/commit/6f62f19fb4adb09186e7e9f7279fa95b5a810077|6f62f19f>` - Merge pull request #157 from Disfactory/release/2.5.0 `<https://github.com/Disfactory/frontend/commit/06a154e7fe8d0a335bd59405c4767b1695ce0050|06a154e7>` - Merge remote-tracking branch 'origin/production'
`<https://github.com/Disfactory/frontend/commit/d87c3c443d382f4a80ac3547ec8645c3ca6c3dee|d87c3c44>` - fix: show "fetching" when landcode is null [#156] `<https://github.com/Disfactory/frontend/commit/4ea3e9f66b0e682909a1687db5b1ce97457fd3a5|4ea3e9f6>` - Merge pull request #160 from Disfactory/yukai/156-landcode
`<https://github.com/Disfactory/frontend/commit/d87c3c443d382f4a80ac3547ec8645c3ca6c3dee|d87c3c44>` - fix: show "fetching" when landcode is null [#156] `<https://github.com/Disfactory/frontend/commit/4ea3e9f66b0e682909a1687db5b1ce97457fd3a5|4ea3e9f6>` - Merge pull request #160 from Disfactory/yukai/156-landcode
`<https://github.com/Disfactory/frontend/commit/d87c3c443d382f4a80ac3547ec8645c3ca6c3dee|d87c3c44>` - fix: show "fetching" when landcode is null [#156] `<https://github.com/Disfactory/frontend/commit/4ea3e9f66b0e682909a1687db5b1ce97457fd3a5|4ea3e9f6>` - Merge pull request #160 from Disfactory/yukai/156-landcode
`<https://github.com/Disfactory/frontend/commit/d87c3c443d382f4a80ac3547ec8645c3ca6c3dee|d87c3c44>` - fix: show "fetching" when landcode is null [#156] `<https://github.com/Disfactory/frontend/commit/4ea3e9f66b0e682909a1687db5b1ce97457fd3a5|4ea3e9f6>` - Merge pull request #160 from Disfactory/yukai/156-landcode
*What's Changed* • fix: check factory layer at rendercomplete event by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/141|#141> • feat: debounce getFactories method by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/142|#142> • fix npm install on m1, remove unused fiber dependency by <https://github.com/bdon|@bdon> in <https://github.com/Disfactory/frontend/pull/151|#151> • Disable clustering at zoom level > 16 [<https://github.com/Disfactory/frontend/issues/150|#150>] by <https://github.com/bdon|@bdon> in <https://github.com/Disfactory/frontend/pull/153|#153> • feat: change protomap url to production by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/154|#154> • feat: add factory followups to ui by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/159|#159> • Release 2.5.0 by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/157|#157> *Full Changelog*: <https://github.com/Disfactory/frontend/compare/2.4.0...2.5.0|2.4.0...2.5.0>
*What's Changed* • fix: check factory layer at rendercomplete event by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/141|#141> • feat: debounce getFactories method by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/142|#142> • fix npm install on m1, remove unused fiber dependency by <https://github.com/bdon|@bdon> in <https://github.com/Disfactory/frontend/pull/151|#151> • Disable clustering at zoom level > 16 [<https://github.com/Disfactory/frontend/issues/150|#150>] by <https://github.com/bdon|@bdon> in <https://github.com/Disfactory/frontend/pull/153|#153> • feat: change protomap url to production by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/154|#154> • feat: add factory followups to ui by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/159|#159> • Release 2.5.0 by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/157|#157> *Full Changelog*: <https://github.com/Disfactory/frontend/compare/2.4.0...2.5.0|2.4.0...2.5.0>
*What's Changed* • fix: check factory layer at rendercomplete event by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/141|#141> • feat: debounce getFactories method by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/142|#142> • fix npm install on m1, remove unused fiber dependency by <https://github.com/bdon|@bdon> in <https://github.com/Disfactory/frontend/pull/151|#151> • Disable clustering at zoom level > 16 [<https://github.com/Disfactory/frontend/issues/150|#150>] by <https://github.com/bdon|@bdon> in <https://github.com/Disfactory/frontend/pull/153|#153> • feat: change protomap url to production by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/154|#154> • feat: add factory followups to ui by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/159|#159> • Release 2.5.0 by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/157|#157> *Full Changelog*: <https://github.com/Disfactory/frontend/compare/2.4.0...2.5.0|2.4.0...2.5.0>
*What's Changed* • fix: check factory layer at rendercomplete event by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/141|#141> • feat: debounce getFactories method by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/142|#142> • fix npm install on m1, remove unused fiber dependency by <https://github.com/bdon|@bdon> in <https://github.com/Disfactory/frontend/pull/151|#151> • Disable clustering at zoom level > 16 [<https://github.com/Disfactory/frontend/issues/150|#150>] by <https://github.com/bdon|@bdon> in <https://github.com/Disfactory/frontend/pull/153|#153> • feat: change protomap url to production by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/154|#154> • feat: add factory followups to ui by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/159|#159> • Release 2.5.0 by <https://github.com/Yukaii|@Yukaii> in <https://github.com/Disfactory/frontend/pull/157|#157> *Full Changelog*: <https://github.com/Disfactory/frontend/compare/2.4.0...2.5.0|2.4.0...2.5.0>
2022-04-21
og:image（長方形）： <https://user-images.githubusercontent.com/8353239/164359415-89b2358b-f52c-4a18-806d-4f218687a48a.jpg|ogimage-100> 分享圖片（正方形）： <https://user-images.githubusercontent.com/8353239/164359427-57e0e56d-d908-480b-b780-381898feb0b7.jpg|square-100>
og:image（長方形）： <https://user-images.githubusercontent.com/8353239/164359415-89b2358b-f52c-4a18-806d-4f218687a48a.jpg|ogimage-100> 分享圖片（正方形）： <https://user-images.githubusercontent.com/8353239/164359427-57e0e56d-d908-480b-b780-381898feb0b7.jpg|square-100>
2022-04-22
`<https://github.com/Disfactory/SpotDiffFrontend/commit/b29a452d9f225b3fd1c09c56947c5d4a0e7f943a|b29a452d>` - feat(tutorial): add component Cut between end of tutorial and start of game `<https://github.com/Disfactory/SpotDiffFrontend/commit/e6fceb790e0ac193dcd18008fb6af2899e926d08|e6fceb79>` - Merge pull request #91 from Disfactory/feat-cut
`<https://github.com/Disfactory/SpotDiffFrontend/commit/b29a452d9f225b3fd1c09c56947c5d4a0e7f943a|b29a452d>` - feat(tutorial): add component Cut between end of tutorial and start of game `<https://github.com/Disfactory/SpotDiffFrontend/commit/e6fceb790e0ac193dcd18008fb6af2899e926d08|e6fceb79>` - Merge pull request #91 from Disfactory/feat-cut
2022-04-23
Bumps <https://github.com/django/django|django> from 2.2.27 to 2.2.28. Commits • <https://github.com/django/django/commit/5c3300027b30c1b498d99010f7d618316f685045|`5c33000`> [2.2.x] Bumped version for 2.2.28 release. • <https://github.com/django/django/commit/29a6c98b4c13af82064f993f0acc6e8fafa4d3f5|`29a6c98`> [2.2.x] Fixed <https://github.com/advisories/GHSA-w24h-v9qh-8gxj|CVE-2022-28347> -- Protected QuerySet.explain(**options) against... • <https://github.com/django/django/commit/2c09e68ec911919360d5f8502cefc312f9e03c5d|`2c09e68`> [2.2.x] Fixed <https://github.com/advisories/GHSA-2gwj-7jmv-h26r|CVE-2022-28346> -- Protected QuerySet.annotate(), aggregate(), a... • <https://github.com/django/django/commit/8352b98e460f1b5349cd8a9a4ce35a573664c7c3|`8352b98`> [2.2.x] Added stub release notes for 2.2.28. • <https://github.com/django/django/commit/2801f29dadbf890206b4cac59a4831f334418bc7|`2801f29`> [2.2.x] Reverted "Fixed forms_tests.tests.test_renderers with Jinja 3.1.0+." • <https://github.com/django/django/commit/e03648f09c9c6be34d977141e33419f5cf72c0d3|`e03648f`> [2.2.x] Fixed forms_tests.tests.test_renderers with Jinja 3.1.0+. • <https://github.com/django/django/commit/9d13d8c10b18da9f8a9a7ea9325c1e2a23279c72|`9d13d8c`> [2.2.x] Fixed typo in release notes. • <https://github.com/django/django/commit/047ece3014f688d64e190f0d0c9845e9a7dd11fa|`047ece3`> [2.2.x] Added <https://github.com/advisories/GHSA-95rw-fx8r-36v6|CVE-2022-22818> and <https://github.com/advisories/GHSA-6cw3-g6wv-c2xv|CVE-2022-23833> to security archive. • <https://github.com/django/django/commit/2427b2fee381e17cd8c72e7c404ec149022fecf1|`2427b2f`> [2.2.x] Post-release version bump. • See full diff in <https://github.com/django/django/compare/2.2.27...2.2.28|compare view> <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/Disfactory/Disfactory/network/alerts|Security Alerts page>.
Bumps <https://github.com/django/django|django> from 2.2.27 to 2.2.28. Commits • <https://github.com/django/django/commit/5c3300027b30c1b498d99010f7d618316f685045|`5c33000`> [2.2.x] Bumped version for 2.2.28 release. • <https://github.com/django/django/commit/29a6c98b4c13af82064f993f0acc6e8fafa4d3f5|`29a6c98`> [2.2.x] Fixed <https://github.com/advisories/GHSA-w24h-v9qh-8gxj|CVE-2022-28347> -- Protected QuerySet.explain(**options) against... • <https://github.com/django/django/commit/2c09e68ec911919360d5f8502cefc312f9e03c5d|`2c09e68`> [2.2.x] Fixed <https://github.com/advisories/GHSA-2gwj-7jmv-h26r|CVE-2022-28346> -- Protected QuerySet.annotate(), aggregate(), a... • <https://github.com/django/django/commit/8352b98e460f1b5349cd8a9a4ce35a573664c7c3|`8352b98`> [2.2.x] Added stub release notes for 2.2.28. • <https://github.com/django/django/commit/2801f29dadbf890206b4cac59a4831f334418bc7|`2801f29`> [2.2.x] Reverted "Fixed forms_tests.tests.test_renderers with Jinja 3.1.0+." • <https://github.com/django/django/commit/e03648f09c9c6be34d977141e33419f5cf72c0d3|`e03648f`> [2.2.x] Fixed forms_tests.tests.test_renderers with Jinja 3.1.0+. • <https://github.com/django/django/commit/9d13d8c10b18da9f8a9a7ea9325c1e2a23279c72|`9d13d8c`> [2.2.x] Fixed typo in release notes. • <https://github.com/django/django/commit/047ece3014f688d64e190f0d0c9845e9a7dd11fa|`047ece3`> [2.2.x] Added <https://github.com/advisories/GHSA-95rw-fx8r-36v6|CVE-2022-22818> and <https://github.com/advisories/GHSA-6cw3-g6wv-c2xv|CVE-2022-23833> to security archive. • <https://github.com/django/django/commit/2427b2fee381e17cd8c72e7c404ec149022fecf1|`2427b2f`> [2.2.x] Post-release version bump. • See full diff in <https://github.com/django/django/compare/2.2.27...2.2.28|compare view> <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/Disfactory/Disfactory/network/alerts|Security Alerts page>.
2022-04-24
`<https://github.com/Disfactory/SpotDiffFrontend/commit/6a38a708ff3ef98da4473a16004e49c16204bb7f|6a38a708>` - feat(ending): add sharing feature `<https://github.com/Disfactory/SpotDiffFrontend/commit/6b7a2d9be92fd0577626b41bbe57b6ecaa949b3a|6b7a2d9b>` - Merge branch 'feat-share-image-0323' of <https://github.com/Disfactory/SpotDiffFrontend> into 0422-share `<https://github.com/Disfactory/SpotDiffFrontend/commit/6bd4fef474b7373cf417f510e26a39f32e25c7c4|6bd4fef4>` - feat(ending): update share image and modify css `<https://github.com/Disfactory/SpotDiffFrontend/commit/fd81c3831793c9df23f826126e360e2f97599a73|fd81c383>` - Merge pull request #92 from Disfactory/feat-share-image-0323
`<https://github.com/Disfactory/SpotDiffFrontend/commit/6a38a708ff3ef98da4473a16004e49c16204bb7f|6a38a708>` - feat(ending): add sharing feature `<https://github.com/Disfactory/SpotDiffFrontend/commit/6b7a2d9be92fd0577626b41bbe57b6ecaa949b3a|6b7a2d9b>` - Merge branch 'feat-share-image-0323' of <https://github.com/Disfactory/SpotDiffFrontend> into 0422-share `<https://github.com/Disfactory/SpotDiffFrontend/commit/6bd4fef474b7373cf417f510e26a39f32e25c7c4|6bd4fef4>` - feat(ending): update share image and modify css `<https://github.com/Disfactory/SpotDiffFrontend/commit/fd81c3831793c9df23f826126e360e2f97599a73|fd81c383>` - Merge pull request #92 from Disfactory/feat-share-image-0323
2022-04-25
2022-04-26
2022-04-27
*Is your feature request related to a problem? Please describe.* We need the product show certain message and image. *Describe the solution you'd like* Set up the OGtitle and OGimage. OGtitle: 大家來找廠｜動手指，拆工廠 OGimage: <https://drive.google.com/file/d/1Zsw0zb4zU7tBE-GG4QQDHy-DMtxA9hDr/view?usp=sharing|https://drive.google.com/file/d/1Zsw0zb4zU7tBE-GG4QQDHy-DMtxA9hDr/view?usp=sharing> <https://user-images.githubusercontent.com/60970217/165514478-7a28fba9-44c4-4ca1-85da-71d5a45cd567.jpg|20220428-1>
*Is your feature request related to a problem? Please describe.* We need the product show certain message and image. *Describe the solution you'd like* Set up the OGtitle and OGimage. OGtitle: 大家來找廠｜動手指，拆工廠 OGimage: <https://user-images.githubusercontent.com/60970217/165514478-7a28fba9-44c4-4ca1-85da-71d5a45cd567.jpg|20220428-1>
@rurumi221 has joined the channel
2022-04-28
開始辨識 - start-game 確認送出 - send-answer 再玩一輪 - play-again 分享 - share 看關於專案 - view-about
開始辨識 - start-game 確認送出 - send-answer 再玩一輪 - play-again 分享 - share 看關於專案 - view-about
因為 GA4 會靠網頁標題分，不知道能不能修改每一頁的標題？ *標題* `${title}="大家來找廠 | 動手指拆工廠 | "` <https://spot.disfactory.tw/#/|https://spot.disfactory.tw/#/> `${title}首頁` <https://spot.disfactory.tw/#/tutorial|https://spot.disfactory.tw/#/tutorial> `${title}教學` <https://spot.disfactory.tw/#/game|https://spot.disfactory.tw/#/game> `${title}辨識` <https://spot.disfactory.tw/#/ending|https://spot.disfactory.tw/#/ending> `${title}結束` *event note（這個已經設定好了）* 開始辨識 - `start-game` 確認送出 - `send-answer` 再玩一輪 - `play-again` 分享 - `share` 看關於專案 - `view-about`
因為 GA4 會靠網頁標題分，不知道能不能修改每一頁的標題？ *標題* `${title}="大家來找廠 | 動手指拆工廠 | "` <https://spot.disfactory.tw/#/|https://spot.disfactory.tw/#/> `${title}首頁` <https://spot.disfactory.tw/#/tutorial|https://spot.disfactory.tw/#/tutorial> `${title}教學` <https://spot.disfactory.tw/#/game|https://spot.disfactory.tw/#/game> `${title}辨識` <https://spot.disfactory.tw/#/ending|https://spot.disfactory.tw/#/ending> `${title}結束` *event note（這個已經設定好了）* 開始辨識 - `start-game` 確認送出 - `send-answer` 再玩一輪 - `play-again` 分享 - `share` 看關於專案 - `view-about`
2022-04-29
Bumps <https://github.com/caolan/async|async> from 2.6.3 to 2.6.4. Changelog _Sourced from <https://github.com/caolan/async/blob/v2.6.4/CHANGELOG.md|async's changelog>._ > *v2.6.4* > > • Fix potential prototype pollution exploit (<https://github-redirect.dependabot.com/caolan/async/issues/1828|#1828>) Commits • <https://github.com/caolan/async/commit/c6bdaca4f9175c14fc655d3783c6af6a883e6514|`c6bdaca`> Version 2.6.4 • <https://github.com/caolan/async/commit/8870da9d5022bab310413041b4079e10db3980b7|`8870da9`> Update built files • <https://github.com/caolan/async/commit/4df6754ef4e96a742956df8782fee27242a2ea12|`4df6754`> update changelog • <https://github.com/caolan/async/commit/8f7f90342a6571ba1c197d747ebed30c368096d2|`8f7f903`> Fix prototype pollution vulnerability (<https://github-redirect.dependabot.com/caolan/async/issues/1828|#1828>) • See full diff in <https://github.com/caolan/async/compare/v2.6.3...v2.6.4|compare view> Maintainer changes This version was pushed to npm by <https://www.npmjs.com/~hargasinski|hargasinski>, a new releaser for async since your current version. <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/Disfactory/license.disfactory.tw/network/alerts|Security Alerts page>.
Bumps <https://github.com/caolan/async|async> from 2.6.3 to 2.6.4. Changelog _Sourced from <https://github.com/caolan/async/blob/v2.6.4/CHANGELOG.md|async's changelog>._ > *v2.6.4* > > • Fix potential prototype pollution exploit (<https://github-redirect.dependabot.com/caolan/async/issues/1828|#1828>) Commits • <https://github.com/caolan/async/commit/c6bdaca4f9175c14fc655d3783c6af6a883e6514|`c6bdaca`> Version 2.6.4 • <https://github.com/caolan/async/commit/8870da9d5022bab310413041b4079e10db3980b7|`8870da9`> Update built files • <https://github.com/caolan/async/commit/4df6754ef4e96a742956df8782fee27242a2ea12|`4df6754`> update changelog • <https://github.com/caolan/async/commit/8f7f90342a6571ba1c197d747ebed30c368096d2|`8f7f903`> Fix prototype pollution vulnerability (<https://github-redirect.dependabot.com/caolan/async/issues/1828|#1828>) • See full diff in <https://github.com/caolan/async/compare/v2.6.3...v2.6.4|compare view> Maintainer changes This version was pushed to npm by <https://www.npmjs.com/~hargasinski|hargasinski>, a new releaser for async since your current version. <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/Disfactory/license.disfactory.tw/network/alerts|Security Alerts page>.
1. 需要將 footer 右下角的 <https://www.cet-taiwan.org/|© 地球公民基金會> 改掉。 ``` 改為 [地球公民基金會](<https://www.cet-taiwan.org/>)與 [<http://g0v.tw|g0v.tw>](<https://g0v.tw/>) 社群共同開發 沒有 all rights reserved 所以不會使用 © ``` 2. 在 footer 左下角的關於此專案 Popup 中希望能加入 1. 大家來找廠全站由使用者辨識產生之資料以 <http://creativecommons.tw/cc0|CC0 公眾領域貢獻宣告> 釋出授權到公眾領域 2. 點位經緯度來自 XXXXX （附網址），衛星空照圖來源為 XXXXX（附網址） 3. 設計圖以 CC-BY姓名標示 4.0 International 釋出，標註「農地違章工廠回報系統貢獻者」，原始碼以 MIT 開放授權公開在<https://github.com/Disfactory|GitHub>上。 Note: 如果覺得設計圖和程式碼的開源條款太煩雜不想列，我們至少一定要列衛星圖資資料來源和 CC0 公眾領域貢獻宣告，設計圖和原始碼的標示，是可以在 about page 找到
1. 需要將 footer 右下角的 <https://www.cet-taiwan.org/|© 地球公民基金會> 改掉。 改為 <https://www.cet-taiwan.org/|地球公民基金會>與 <https://g0v.tw/|g0v.tw> 社群共同開發 沒有 all rights reserved 所以不會使用 © 2. 在 footer 左下角的關於此專案 Popup 中希望能加入 大家來找廠全站由使用者辨識產生之資料以 <http://creativecommons.tw/cc0|CC0 公眾領域貢獻宣告> 釋出授權到公眾領域 衛星空照圖來源為 設計圖以 CC-BY姓名標示 4.0 International 釋出，標註「農地違章工廠回報系統貢獻者」，原始碼以 MIT 開放授權公開在<https://github.com/Disfactory|GitHub>上。
`<https://github.com/Disfactory/license.spot.disfacotry.tw/commit/26edd951b9679f640261e448703b7a6ce387f540|26edd951>` - chore:clone from about `<https://github.com/Disfactory/license.spot.disfacotry.tw/commit/868205919a3837d61a2661262547fb5e0c5c8b82|86820591>` - feat:home page available `<https://github.com/Disfactory/license.spot.disfacotry.tw/commit/1ca20ab6a8fd623f25c04fc4a873710eaaca67f7|1ca20ab6>` - fix:wrong page title `<https://github.com/Disfactory/license.spot.disfacotry.tw/commit/7d77ca9f258570537ff1cacf2e0b0fff02b508b6|7d77ca9f>` - fix:list indent use 2 spaces `<https://github.com/Disfactory/license.spot.disfacotry.tw/commit/85475fd576ce1e263bdf809ce4224311b55a459b|85475fd5>` - style:formatting `<https://github.com/Disfactory/license.spot.disfacotry.tw/commit/abf4247b840f15ccef9e751a30bbc781d2480c7b|abf4247b>` - style:formatting `<https://github.com/Disfactory/license.spot.disfacotry.tw/commit/c129fd5d1c035ab77539e8051ea4efa68aad4689|c129fd5d>` - style:formatting
`<https://github.com/Disfactory/license.spot.disfacotry.tw/commit/26edd951b9679f640261e448703b7a6ce387f540|26edd951>` - chore:clone from about `<https://github.com/Disfactory/license.spot.disfacotry.tw/commit/868205919a3837d61a2661262547fb5e0c5c8b82|86820591>` - feat:home page available `<https://github.com/Disfactory/license.spot.disfacotry.tw/commit/1ca20ab6a8fd623f25c04fc4a873710eaaca67f7|1ca20ab6>` - fix:wrong page title `<https://github.com/Disfactory/license.spot.disfacotry.tw/commit/7d77ca9f258570537ff1cacf2e0b0fff02b508b6|7d77ca9f>` - fix:list indent use 2 spaces `<https://github.com/Disfactory/license.spot.disfacotry.tw/commit/85475fd576ce1e263bdf809ce4224311b55a459b|85475fd5>` - style:formatting `<https://github.com/Disfactory/license.spot.disfacotry.tw/commit/abf4247b840f15ccef9e751a30bbc781d2480c7b|abf4247b>` - style:formatting `<https://github.com/Disfactory/license.spot.disfacotry.tw/commit/c129fd5d1c035ab77539e8051ea4efa68aad4689|c129fd5d>` - style:formatting
2022-04-30