mirror of
https://github.com/waku-org/js-waku.git
synced 2025-02-24 10:08:15 +00:00
54 lines
1.4 KiB
Markdown
54 lines
1.4 KiB
Markdown
|
---
|
||
|
|
name: "\U0001F680 Feature request"
|
||
|
|
about: Suggest an idea for this project
|
||
|
|
title: 'feat:'
|
||
|
|
labels: ''
|
||
|
|
assignees: ''
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
<!--
|
||
|
|
Delete not needed sections below.
|
||
|
|
-->
|
||
|
|
|
||
|
|
### Description
|
||
|
|
<!--
|
||
|
|
What problem are you facing, or what improvement are you suggesting?
|
||
|
|
- Clearly describe the problem or need.
|
||
|
|
- Explain why this feature would be useful.
|
||
|
|
-->
|
||
|
|
|
||
|
|
### User Story
|
||
|
|
<!--
|
||
|
|
Describe the feature from the perspective of the user. Use the following format:
|
||
|
|
- As a [type of user], I want to [do something], so that [reason/benefit].
|
||
|
|
|
||
|
|
Examples:
|
||
|
|
- As a developer, I want to see detailed error logs, so that I can debug issues more effectively.
|
||
|
|
- As a user, I want to be able to subscribe to a content topic without manually specifying a peer.
|
||
|
|
-->
|
||
|
|
|
||
|
|
### Proposed Solution / Feature Design
|
||
|
|
<!--
|
||
|
|
Describe how the feature should work.
|
||
|
|
- Provide a high-level summary of the solution.
|
||
|
|
- Include details on the behavior, user interaction, and functionality.
|
||
|
|
-->
|
||
|
|
|
||
|
|
#### Optional: Diagram or Draft of Design
|
||
|
|
<!--
|
||
|
|
If applicable, include visual aids or drafts to clarify your proposal.
|
||
|
|
- Attach diagrams or design drafts to illustrate your idea.
|
||
|
|
|
||
|
|
Use Mermaid syntax - https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams
|
||
|
|
-->
|
||
|
|
|
||
|
|
### Notes
|
||
|
|
<!--
|
||
|
|
Anything relevant:
|
||
|
|
- issues or previous features;
|
||
|
|
- discussion threads;
|
||
|
|
- docs;
|
||
|
|
- features in other projects;
|
||
|
|
-->
|