class: Topic 各種唔同提議

[09milk]

hkug/hkug-backend-node/src/domains/Topic.js

Lines 1 to 15 in 0eb12f2

	export default class Topic {
	constructor({
	id,
	forum,
	category,
	title,
	createdDate,
	authorId,
	authorName,
	lastReplyDate,
	totalReplies,
	like,
	dislike,
	totalPage,
	} = {}) {

• authorId: 會唔會係冇用嘅資料? 大部份topic list都只係display個author名就夠

• category: 如果係user轉台先攞topic list, category會唔會次次攞都一樣?

• id: 係就咁一個integer, 定係一個hash(forum, url)

• authorGender: hkg/lihkg 手機version都有出topic果時出埋author係巴定絲

• url: 我提議記錄埋topic指向嘅url, 因為user click入去果時應該會用到個url
  hkg - https://m.hkgolden.com/view.aspx?message=6887195&type=YY (YY係category, 係optional)
  lihkg - https://lihkg.com/thread/XXXXXX/page/1
  應該只係記低XXXXXX果part就夠

[ghost]

authorId: Depends on where we will have a user info/detail display function. Keep for future updates.

category: Yes if got from list topics API. Useful as the API consumer no need to save the request parameter by themselves. Otherwise this information will be lost after the request. Also useful when getting by topic id. Keep.

id: whatever the backed API (lihkg or hkg) returns to identify this topic.

authorGender: Will add!

url: Already included all information in order to construct the url (id + category), no need to duplicate.

[09milk]

咁嘅話id就唔係unique (hkg/lihkg可以撞id), 對我地自己做記錄會唔會唔方便(回帶之類嘅function)

[ghost]

1. 暫時冇打算儲佢地啲文係自己DB, 可能有法律問題

2. 所以仲有forum呢個key, forum + id就唔會撞(forum=[HKG, LIHKG])

3. 應改名做topicId之類避免誤會