Skip to content

feat: add Waline comment system support - #169

Open
guohoo wants to merge 1 commit into
wangchucheng:mainfrom
guohoo:master
Open

feat: add Waline comment system support#169
guohoo wants to merge 1 commit into
wangchucheng:mainfrom
guohoo:master

Conversation

@guohoo

@guohoo guohoo commented Mar 7, 2022

Copy link
Copy Markdown

Because of security, I want to add Waline comment system support, and it adapted for dark mode.

@wangchucheng

Copy link
Copy Markdown
Owner

Hi @guohoo,

Thanks for your contribution! Can you also write the related docs here? After that I can review it.

@guohoo guohoo closed this Mar 9, 2022
@guohoo guohoo reopened this Mar 9, 2022
@guohoo

guohoo commented Mar 9, 2022

Copy link
Copy Markdown
Author

OK, but it may not start until this weekend. I am preparing for my exam recently.

@wangchucheng

wangchucheng commented Mar 9, 2022 via email

Copy link
Copy Markdown
Owner

@wangchucheng wangchucheng left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution! Just some points above.

new Waline({
el: "#waline-comments",
requiredMeta: [ 'nick','mail' ],
dark: "html[class=\"fontawesome-i2svg-active fontawesome-i2svg-complete dark\"]",

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need the fontawesome-i2svg-active fontawesome-i2svg-complete here? Eureka only uses dark to indicate that it is dark mode.

And maybe we need to make it configurable and add a new possible value (maybe eureka) to do this instead of doing it by default. You can refer to how utterances in eureka handles this.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's really not elegant enough here, I think it would be better to change it to dark: "html.dark".

@guohoo guohoo Mar 18, 2022

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And make it configurable is a good idea, but I think move dark: "html.dark" to params.yaml maybe more concise. Just leave it blank when don't need it.

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And you also need to handle the possible duplication of this param since you manually added it and users may set it in config.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants