Add value: property to the attributes: under id: description in bug.yaml Issue template.
Changes need to add
This complete thing needs to be added
value: | ### what is the problem? ### what is your suggested solution?
After changes
The template will look like this after the addition.
- type: textareaid: descriptionattributes:
label: Descriptiondescription: A brief description of the question or issue, also include what you tried and what didn't workvalue: | # This will get added ### What is the problem? ### What is your suggested solution?validations:
required: true
Problem
Right now when we make any updates to the JSON profile it gives us a message saying "*.json file updated successfully" but the same thing is also printed when no updates are made.
Potential solution
A message like "No updates were made" should be printed instead.
Some of the dependencies we using are old versions and some are highly vulnerable. To use the lastest version we need to start using the ES6 standards.
We no longer need the avatar and displayStatsPublic keys for creating LinkFree profile. We have to remove it from the createUser.js and questions.js util files. I would like to work on this.
Problem
Right now we are not allowing users to add group or color keys for their links since they are optional.
Potential solution
While creating profile we can ask users for the group and color keys if they want to add them or not for that particular link. Also need to do something similar for updating the link in future where we would have to check whether that link has a group or not (same for color key); if it does then giving user the option to update it.
Problem
When selecting icons for adding to the link or milestones we have to scroll through this entire list which is quite cumbersome.
Potential solution
It would be great if we can take input from user and create a search filter instead. This will reduce time to search for the desired icon. They can just type in the name of the icon and matched icons will show up to select from.
Currently when the users are allowed to overwrite their profile we are asking them to write everything from scratch. How about also asking them if they want to keep that field as it is? If not then they can overwrite or add anything they want to.
Instead of using whole sentences for switch cases while selecting choices. We can store them as key value pairs and reference them using constants as:
Example : const choices = {CH1: "This is a demo choice sentence"};
and case choices.CH1;