-
Notifications
You must be signed in to change notification settings - Fork 112
Feature/location #1254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/location #1254
Conversation
add new locations and removed locations that will not be used this year.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1254 +/- ##
==========================================
- Coverage 74.67% 74.59% -0.09%
==========================================
Files 84 84
Lines 3171 3184 +13
==========================================
+ Hits 2368 2375 +7
- Misses 803 809 +6 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Ritabear
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
src/events/api/views.py
Outdated
| def custom_event(self) -> bool: | ||
| if isinstance(self.obj, CustomEvent): | ||
| return not self.obj.break_event and self.obj.link_path != '' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto: function 做的事情和 custom_event 這個命名不符
"Custom Event" 是一種 event type,而 "Break Event" 是它的一個 break_event attribute 都為 true 的子集,但這個 property 卻只有在 self.obj 為「非 break event 的 custom event」才是 true
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test cases?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
這東西當初沒有溝通好,所以又是一張這兩天必須完成的票
議程組還要上去打議程資訊
所以測試我請他之後補
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
這個 EventWrapper 本來就還沒有測試
https://app.codecov.io/gh/pycontw/pycon.tw/pull/1254/blob/src/events/api/views.py#L142
| SPT_OS = '81-spt-os' # sprint / open space | ||
| TUTORIAL = '82-tutorial' # tutorial | ||
| YI_PS = '83-yi-ps' # young inspire / poster session |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
過去都是用 location 名稱 (會議室編號) 來作為選項,為何這裡會用活動名稱作為選項?
(送到前端傳達的意思變成「tutorial(活動)在 tutorial(地點)舉辦」,這樣是預期的嗎?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
是 今天的scedule變動比較大,然後這些都要單獨一個一軌,名稱就是location,然後給議程組設定活動
前端部分會像coscup
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
前端對於活動地點的資訊會如何呈現呢?有設計稿或者任何文字說明嗎?
我現在比較難想像後端這樣修改之後前端要怎麼使用這些資訊
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
送到前端傳達的意思變成「tutorial(活動)在 tutorial(地點)舉辦」,這樣是預期的嗎?
我覺得這樣就是會產生這個問題XD
不過這不是程式問題, not a PR blocker,要跟 stakeholder 確認這是預期行為及可能發生的問題
時間也是不是pycon 以往切死的時間段
有更多說明嗎(什麼意思、預期怎麼實作)?
「切死的時間段」指的是「 schedule 頁面上 slot 長度大致與活動時長成正比」還是「schedule 頁面上橫軸位置大致代表時間點」?我覺得這兩件事任一被改掉都只會對 UX 有負面影響
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
會把一個活動 EX: tutorial 標記為是在「tutorial」這個地點舉辦。是當初PM跟我們說的
他們到時候會在教室外面貼這是tutorial地點
目前每個活動時長不一、可以有彈性,slot 不再強制對齊 (schedule 頁面上 slot 長度大致與活動時長成正比) 會像是google calender 一樣,時間多長就佔多長的bolck 跟位置
這兩個都是今年新需求
不知道有沒有回答到><
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
但是 google calendar 是完全的 slot 長度與活動時長成正比,過去的 schedule 頁面也是時間比較長就會有顯示比較長的 slot (只是 DB 的 "Time" table 就要塞好每個時間點),所以我看不出你描述的差異是什麼?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
我們有discord 回覆><
5ec1741 to
f9e61b3
Compare

Types of changes
Description