opengenus / cosmos-search

:seedling: The next generation unbiased real-time privacy and user focused code search engine for everyone; Join us at https://discourse.opengenus.org/

Cosmos Search

This is the real-time code search engine for all. We aim to revolutionize the way people interact and search for code. This is evident in our on-going work. Cosmos Search is privacy-focussed as we do not store any data.

Some of our core beliefs that drive the development of this search engine:

• Searching is more of a social act.
• The Divide between programming languages and native languages must be minimized.
• Time spend on searching must be minimized.
• Time spend on learning, discussing and socializing must be maximized.

Link: search.opengenus.org

Cosmos Search is one of the most impactful sister projects of Cosmos powered by OpenGenus Foundation.

This is the official search tool for cosmos, a library of every algorithm and data structure code that you will ever encounter.

Maintainers

This is a very ambitious project based on a massive collaboration and to keep the quality intact and drive the vision in the proper direction, we have maintainers.

Maintainers are your friends forever. They are vastly different from moderators.

Currently, we have 3 active maintainers and we are expanding quickly.

The task of maintainers is to review pull requests, suggest further quality additions and keep the work up to date with the current state of the world. 🌍

Let us know if you would like to be a maintainer and we will review and add you upon subsequent contributions. To join our massive community at Slack open an issue here.

Contributors

The success of our vision depends on you. Even a small contribution helps. All forms of contributions are highly welcomed and valued.

When you contribute, your name with a link (if available) is added to our contributors list.

You can contribute by writing code, documentation, making Cosmos search friendly and many others. There are endless possibilities.

You might, also, like to take a look at our Ideas List. You can take up a task from the list or suggest your own. Open a pull request to indicate the work you are doing.

Feel free to discuss anything with us. 💭

Contributing to the Human-Curated Lists

One can contribute to the lists by uploading their files to the repository human_curated_lists which supports only .md file(s) for now.

After uploading the file(s) update the lists.json file with necessary details about the list such as List Title, List Description, Author Name, etc.

After this a Pull Request can be generated and the lists will be reviewed and merged.

Technologies Used

This project uses a number of open source projects:

• Django - Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
• Bootstrap - Responsive frontend framework
• Heroku - Webapp deployed here
• Travis - Continuous Integration of the project

Run this search engine locally

1. Clone this repository using

   $ git clone https://github.com/OpenGenus/cosmos-search.git
   

2. Go inside main Django app

   $ cd cosmos-search
   

3. Setup a virtual environment

   $ virtualenv -m python3 env_name OR $ python3 -m venv env_name

   (For Conda users)

   $ conda create -n env_name python=3.6 anaconda

4. Activate the virtual environment

   $ source env_name/bin/activate
   

   The virtual environment can be deactivated with the deactivate command.

   (For Conda users)

   $ source activate env_name

   The virtual environment can be deactivated with the source deactivate command.

5. Install local dependencies

   Conda users need to install pip locally in their virtual environment using $ conda install pip

    pip install -r requirements.txt
   

6. Create a project in the Google Developers Console and obtain authorization credentials and API Key for YouTube Data API v3.

7. Insert the obtained Key in parameter DEVELOPER_KEY in .env.example file

8. Copy the .env.example file to .env and supply values for the required variables.

9. Collectstatic files using

   $ python manage.py collectstatic
   

10. Migrating files using

    $ python manage.py migrate
    

11. Create Cache Table

    $ python manage.py createcachetable
    

12. Run the app

    $ python manage.py runserver
    

13. View the locally built site

    localhost:8000
    

To run the web app in Debug mode set the DEBUG environment variable. In Linux, run the export DEBUG=True command in the terminal.

License

We believe in freedom and improvement. Cosmos Search is built with ♥ by OpenGenus Community under GPL v3

cosmos-search's Issues

Page not found error while opening code files

I'm submitting a ...

• bug report
• feature request

Description:
There is bug in redirecting link of code files. It shows "error 404 Web Page in not found".

Expected Behaviour:
When we click on any code shown in solution drop down, it should redirect to GitHub page where the code is present.

Actual Behaviour:
On clicking to the code, it is showing page not found error.

Steps to Reproduce:
Search for any code in search-bar
From solutions drop down menu try to open any code.

**Screenshots **:

Would you like to work on this issue?

• Yes
• No

static_root is not defined

I'm submitting a ...

• bug report
• feature request

Description:
There is no static_root defined. Hence, it is creating problem whenever we are running command python manage.py collectstatic .

Expected Behavior:
The collectstatic management command should collect static files into the mentioned directory.

Actual Behavior:

Steps to Reproduce:

• run the command python manage.py collectstatic

Would you like to work on this issue?

• Yes
• No

Imporve readme

Right now readme donesnot contain instructions to deploy locally

Lot of unwanted files present in this repo

Include search results from trusted sites

I'm submitting a:

• bug report
• feature request

Description:

Include results from other trusted sites for a search term in addition to our current results.

To begin with, we may consider the following trusted sites:

• Wikipedia
• Tutorialspoint
• Stackoverflow

To fetch results, we may use create a crawler to crawl trusted sites or scrape the data from a search engine.

You may fetch a few of the top results from a search engine like Google. For a specific site, use search terms like linear search site:wikipedia.org. The number of results should vary for various sites. For instance, we can provide 1 Wikipedia result, 2 Tutorialspoint result and 4 StackOverflow results. This approach will have limitations so, we can cache results to avoid unnecessary scraping.

The ideal cached results may include the url and the metadata to enable further searches. Implementing this will include a scraping code to present results to users during searching.

Caching can be taken care of in a separate feature. For caching, a separate script can be used to collect results for a set of keywords and store it in a database. Additionally, searching should include our cached results as well.

This feature will make Cosmos-Search more usable in general and help us provide a complete learning experience. 👍

Update .gitignore

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:
Some directories needs to be added and updated in .gitignore.

Expected Behavior:
The mentioned directories should not be tracked by git.

Actual Behavior:

Steps to Reproduce:
Build the project locally, then check git status.

Would you like to work on this issue?

• Yes
• No

Suggestions based on a search result for further exploration

This is a:

• bug report
• feature request

Description:

Generate suggestions for a particular search result. This will aid one to proceed to learn a new topic related to the initial topic.

For instance, the initial search may be for linear search. In this case, the suggestions may be fibonacci search, fuzzy search, binary search and the like.

This requires to pick up a folder that is on the same level as the folder for the initial search and top 5 results may be randomly (or based on a particular criterion) selected.

Voting feature for anonymous users

This is a:

• bug report
• feature request

Description:

Add a voting feature ⭐ that works for anonymous users.

For this, you may assign a voting to each category of codes in the meta-data. When a user votes for a particular search result, store the vote assigned along with the IP address of the user in a database. On displaying, calculate the average vote and display it.

This will provide a social feature and provide some interactivity.
We will provide more social searching feature soon as the user profile and authentication system are ready. The anonymous social features will be permanent as everyone deserves to enjoy a good search. 👍

Not getting all matching results when searching

Hello everybody,

I'd like to thank you for your work. I submit here my first issue in this repository.

I'm submitting a ...

• bug report
• feature request

Description:

I have tried to search for round robin in Cosmos search.

Expected Behavior:

All implementations of round robin in Cosmos.

Actual Behavior:

Getting just two implementations instead of three. Here are the implementations, the first one isn't appearing.

Steps to Reproduce:

• Enter round robin in Cosmos search.

Would you like to work on this issue?

• Yes
• No

Updated README for Anaconda (Conda) Users

I'm submitting a:

• bug report
• feature request

Description:

While setting up the search engine locally, Anaconda Users might face a problem while installing requirements.txt in their virtual environment (as conda users cannot use virtualenv -m python3 env_name), I have a fix for this and would like to open a PR with an updated README.md

Expected Behaviour:

All the packages in the requirements.txt file are installed with the help of the command conda install --yes --file requirements.txt .

Actual Behaviour:

Solving Environment: Failed
Some packages are not installed.

Steps to Reproduce :

Create environment using conda create -n yourenvname python=x.x anaconda and install requirements.txt using conda install --yes --file requirements.txt

Would you like to work on this issue?

• Yes
• No

count of solutions for search results

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:

Whenever we search for a query, the results for each directory path come in dropdown. It would be better if the user could see the number of solutions in each result so he/she can better select the solution box to pick first.

Expected Behavior:

There will be count of number of solutions for each path, so the user can directly first see from what he/she feels is the most relevant search item.

Actual Behavior:
Currently the user has no way on knowing how many solutions are there in each dropdown without manually checking each.

Steps to Reproduce:
Search merge sort, the 3 search results have 1,3 and 19 solutions each.
Screenshots (if any):

Would you like to work on this issue?

• Yes
• No

Should we add a linting tool?

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:

A linting tool like flake8 is necessary to have the code live in the repository in a proper way and to have a good code base.

Expected Behavior:

A linting tool should be implemented and the current linting issue should be resolved.

Actual Behavior:

No linting tool, so the code doesn't follow PEP8 guidelines

Would you like to work on this issue?

• Yes
• No

Authentication

I'm submitting a ... (check one with "x")

• feature request

Description:
We can store user's search history similar to you tube,Chrome etc in order to make cosmos search more user specific.For doing this we may need to ask user to sign in with gmail or something else. As stated by @AdiChat "If we store user history, we can create exciting new features like personalized learning paths, develop the mental model of the user based on knowledge gained and many more. "

For this, I would like to start with the basic outlay for creating the authentication system and store the search history.

Would you like to work on this issue?

• Yes
• No

Unable to install requirements.txt with conda virtual env

Description:
Unable to install python-decouple with conda.
Gives a package not found error.

Incorrect Links for Algorithms github code

Go to http://search.opengenus.org/query/?q=byte

The first search result would be bit-manipulation/byte_swapper .
Click on solution dropdown and then on ByteSwapper.java .
It will take you to an incorrect link i.e. https://github.com/OpenGenus/cosmos/blob/master/code/bit-manipulation/byte-swapper/ByteSwapper.java

But it should be https://github.com/OpenGenus/cosmos/blob/master/code/bit-manipulation/byte_swapper/ByteSwapper.java

The random keywords in search box aren't always having a search result

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:

Some of the random algorithms that show up in the search box whenever cosmos-search is refreshed aren't having search results.

Actual Behavior:

Only those algorithms that are having solutions should show up in the search box.

Would you like to work on this issue?

• Yes
• No

Allow search query with leading, trailing and extra in between spaces.

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:
It raises an error on searching a query with leading, trailing, and extra spaces in between the words of a query.

Expected Behavior:
Allow a consistent query search. It should provide results of words with or without extra spaces.

Actual Behavior:
Query search is not consistent.
e.g. query: .... sort or sort...... or .......sort or ...quick.......sort raises result not found error currently.
Here . is representing whitespace.

Steps to Reproduce:

• Type any query with extra spaces.

Would you like to work on this issue?

• Yes
• No

Generate the list of tags

I'm submitting a:

• bug report
• feature request

Description:

Create a list of tags that will help in developing several other features. To create the list of tags, you may use the folder name as a tag and dynamically, generate the list of tags.
Consider the following path: code/search/src/linear_search:For this path, we will get two tags search and linear search.

Just like the meta-data, the list of tags is expected to be stored in a similar format for further use.

This will give us the ability to organize our search results in a better way.

Updated the method of loading json files(Windows users).

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:
While setting up the search engine locally, I encountered an issue regarding the loading of json file in windows which was occuring due to different encoding formats. The error shown was
UnicodeDecodeError 'charmap' codec can't decode byte 0x90 in position 127: character maps to <undefined>

Expected Behavior:

All the features should be running without any error.

Actual Behavior:

Shows error when accessing lists and calculator section of the search engine.

Steps to Reproduce:
Changing the loading method by adding the specific encoding format for the json file.
f = open(settings.LISTS_INFO, 'r', encoding='utf8')

Screenshots (if any):
https://imgur.com/b3au9Ab
Would you like to work on this issue?

• Yes
• No

correcting the input in search box in header.html

DISCRIPTION:
In the search box ,there is a correction to be made as the"algo-name"it is not being removed when we start typing.

SCREENSHOTS:

Would you like to work on this issue?
YES

Add ability to share a page

I'm submitting a:

• bug report
• feature request

Description:

Incorporate the ability to share a page/ search result to social media platforms. The sharing icons may appear below the search bar that is adjacent to the result information (Showing 1 results for: linear search for search term linear search).

Initially, you may support 3 platforms namely: Twitter, Google+ and Facebook.

This will be a convenient feature to share a result with the user's community and will be a small step towards moving searching to social which is one of our core missions.

Section to add code to missing algorithm.

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:
A section can be provided where code to some missing algorithms can be added as well as others can upvote or downvote this code or comment if there is any bug present.

Would you like to work on this issue?

• Yes
• No

Display code in search engine instead of redirecting

I'm submitting a:

• bug report
• feature request

Description:

Instead of redirecting to GitHub for every code result, we can fetch the code from the server and display it in a new page.

The code base (that is Cosmos) is maintained at the server side as a part of the meta-data update process. You may, also, fetch the raw code data from GitHub (instead of server) if convenient.

Consider a code for linear search having a path code/search/src/linear_search/linear_search.rs. Currently, we direct the user to this url but the target is to direct the user to an url like search.opengenus.org/code/search/src/linear_search/linear_search.rs or search.opengenus.org/code?q=search/src/linear_search/linear_search.rs which will render the code.

If the users can view the code within the search engine, then the user retention rate will be increased and the learning process can be centralized to Cosmos-Search. You need to use an appropriate syntax highlighter (like prism.js) for this feature.

No Favicon support for website

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:

There's a favicon for cosmos-search but it's not showing up on the website. It has to be added.

Expected Behavior:

Show OpenGenus logo as favicon.

Would you like to work on this issue?

• Yes
• No

Random pre-filled search bar

This is a:

• bug report
• feature request

Description:

Randomly load a search term to aid the user to move further. User may be a beginner or may be at a loss of search terms.
This is aid anyone to randomly learn a topic.

For instance, the search bar may be pre-filled with a search term say binary search. For this point, user will have two options:

• Press enter to explore the randomly selected topic
• Enter the search term user is thinking of.

This requires to pick up a folder name from the metadata.json and display it is the search bar in an appropriate format.

Include videos as a search result

I'm submitting a:

• bug report
• feature request

Description:

Include video results 📺 for a particular search term.

For this, you may use the Youtube API. A tab named videos under the search bar should appear. On clicking on the tab, video results will appear sequentially (4 results in a row). You may limit to top 50 results.

You may use the official Google python client to achieve this.

This feature will enhance the user experience as videos form a central part of daily learning and there has been a rapid rise of learning resources at YouTube. As an enhancement, we plan to provide recommendations from trusted creators in future features. This will form the basis of a new learning experience. 👍

Styling editor theme

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:
Customising the code space.

Expected Behavior:
This might improve the visual appearance of the code space and make it suitable to user's preference.

Actual Behavior:
The user can toggle between the themes accordingly.

Screenshots (if any):

Would you like to work on this issue?

• Yes
• No

What is this project about?

Add support for human-curated lists

I'm submitting a:

• bug report
• feature request

Description:

Create a template/ system to serve human-curated lists 📖.

The list will be in json formats and will contain a list of links along with title and description. There will be sub-sections and each sub-section will contain links. There may be several such lists. Consider a list for "best resources to learn Go" denoted by learn_go.json file. For this, sub-sections may be "websites", "youtube", "free tutorials", "paid courses" and others.

The list must be available at search.opengenus.org/list/learn_go. In fact, it follows the following pattern: search.opengenus.org/list/{list_name}.

Sample JSON format:

{
	"title": "",
	"id": "",
	"tags": [],
	"link": "",
	"credit_link": "",
	"short_description": [],
	"long_description": [],
	"date": "",
	"authors": ["",""],
	"section": [
		{
			"sub_section": "",
			"id": "1.1",
			"short_description": "",
			"long_description": "",
			"tags": [],
			"grand_section": [
				{
					"title": "",
					"id": "1.1.1",
					"short_description": "",
					"long_description": "",
					"link": "",
					"tags" [],
				},
				...
			]
		},
		...
	]
}

You are free to use another JSON format as well.

This includes creating a template and routing for such a sample list. From the UI point of view, the sub-sections must be presented to the user. When the user clicks on a sub-section title, it must expand and the contents must be visible.

This will greatly enhance the user experience and reduce searching time by providing human curated links and knowledge. These lists will be presented as search results. This will form the basis for further exciting updates that will pave the way to a faster search. 👍

Incorrect metadata generated due to inconsistent folder structure

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:

Metadata is not generated correctly because of inconsistent folder structure and the code is not able to handle that situation.

Expected Behavior:

Correct metadata should be generated, if possible, irrespective of the folder structure. There may be a strict folder structure for the cosmos project.

Actual Behavior:

Folder structure --

cosmos/code/ operating_system/src
|-- scheduling
|    |-- round_robin_scheduling
|         |   round_robin_scheduling.cpp
|         |   round_robin_scheduling.java
|         |-- round_robin_c
|              |  README.md
|              |  queue.h
|              |  queue.c
|              |  round_robin.c

Metadata generated: "operating_system/src/scheduling/round_robin_scheduling/round_robin_c": ["README.md", "queue.h", "round_robin.c", "queue.c"]

Steps to Reproduce:

See the metadata.json file

Would you like to work on this issue?

• Yes
• No

Back Button

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:

If I go for searching anything there is no back button on the page to return to previous or home page.

Would you like to work on this issue?

• Yes
• No

more modern logo with letter C and code symbol

I think you need more modern logo. what you think of my design? I can change color and upload svg file if you like it

Add computational power

I'm submitting a:

• bug report
• feature request 🏆

Description:

We must provide some computational 💻 power to the search engine. We must define a set of search keyword formats and on matching, we must trigger the corresponding computation and present the result.
For instance, if the user searches 2*5 or 2 X 5, we must return 10. 📅

Basic operations such as addition, subtraction, multiplication, division, modulus, square root, trigonometric operations and others can be supported in the initial version.

Having computational power will improve the usability of the engine and will be used as a basis for further exciting features.

Let us know if you would like to work on this. 👍

Issue and PR template

New logo for Cosmos-Search

Hello, I designed several logos for cosmos search. If you like any of these, I will send you a pr and files.

Also, If there's anything you want, I can design it.

Add instructions for inserting YouTube API credentials

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:
To run the project locally, user should have instructions to ease the installation.

Expected Behavior:
Few instructions needs to be provided in README for guiding user to insert YouTube API credentials and create a cache table.

Actual Behavior:
Currently following the given set of instructions provides internal server error while running project locally.

Steps to Reproduce:
Run the project locally with given instructions.

If relevant, please include screenshots and logs.
Not applicable

Would you like to work on this issue?

• Yes
• No

Solutions dropdown in each solution view

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:
Currently, whenever we search for a query, we get compiled search results in different cards. When a user clicks on a particular solution from the dropdown, he/she is redirected to another page with that solution. However is the use wants to see the same solution implemented in different language, he/she has to go back and select one from the previous page.

Expected Behavior:
We can have a dropdown on the page displaying the code, so that it is easier for the user to see solution in different languages.

If relevant, please include screenshots and logs.

Screenshots (if any):

Would you like to work on this issue?

• Yes
• No

Add a command to setup virtualenv in the Readme file.

I would like to request a change in the Readme file.
I'm submitting a ...

• bug report
• feature request

Description: Correct me if I'm wrong, but I think setting up a virtualenv is mandatory before running the search engine locally. Curently, there is no mention of creating a virtual environment in the Readme instructions. Even though it's quite obvious, I think mentioning it in the instructions will be helpful to new contributors.

Would you like to work on this issue?

• Yes
• No

Remove test cases from search results

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:

If I search up something such as test in the search, I get results that include the testing of the algorithms in cosmos. Users don't really care about this, so such results should be filtered out.

Expected Behavior:

N/A

Actual Behavior:

You see test results

Steps to Reproduce:

• Search up test in the search. Some results are from the test folder of cosmos.

Screenshots (if any):

Would you like to work on this issue?

• Yes
• No

Is there anyway I can participate in OpenGenus?

I got the invite like last week, but the link expired by now.

Comments Section

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:

While using cosmos-serach if user found some algorithm missing he could comment or give feedback for making this product better.

Would you like to work on this issue?

• Yes
• No

__pycache__ should be in .gitignore

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:

pycache should be in .gitignore. It is not meant to be in the git repo.

Expected Behavior:

pycache should be in .gitignore and not in the repo

Actual Behavior:

pycache is not in .gitignore.

Steps to Reproduce:

Check the cosmos-search folder.

Screenshots (if any):

Would you like to work on this issue?

• Yes
• No

The 'Travis' build is failing

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:
While we working with database the python manage.py test is not executing.
The Travis build is failing because there are no commands regarding makemigrations and migrate in travis.yml.
Expected Behavior:

Actual Behavior:

Would you like to work on this issue?

• Yes
• No

Real-time search suggestions

I'm submitting a:

• bug report
• feature request

Description:

Using the list of tags, give user real-time search suggestions as the user types.
The suggestions will contain results from the list of tags and can be generated by string matching.

Consider the user types l in the search bar, then the suggestions will be: longest_palindrome sequence, Longest Bitonic Sequence, longest increasing sequence, Longest Increasing Subsequence, ... , linear programming, linear search and many others.
As the user goes on to type the next letter (that is i), then the suggestions are reduced to linear programming, linear search and others.

Also, note that we may display only 10 real-time suggestions which are randomly selected from the list of suggestions.

This feature is dependant on the feature mentioned in the previous issue #39 (which must be done first ideally)

This feature will enhance the user experience and will aid learners in discovering new topics and aid faster search.

The search box needs to be cleared before giving a new query

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:
We have to clear search box every time before entering a new query.

Expected Behavior:
The search box should be cleared if the user wants to enter a different query.

Actual Behavior:
The search box is filled with the suggestion which the user has to clear every time.

Steps to Reproduce:
The suggestion should be pre-selected ( like google search bar ) so that the search box is cleared and enables the user to give a new query or if the user presses enter, the page gets directed to the suggestion.

Screenshots (if any):

Would you like to work on this issue?

• Yes
• No

Adding .editorconfig to maintain consistent coding style across whole project.

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:

• EditorConfig helps to define and maintain consistent coding styles between different editors and IDEs.
• It will help to bring consistency in the project, and reinforces fixed and valid set of styles to be followed across, while making any changes in the project.

Expected Behavior:
Following specific set of coding style for having consistency across the whole project.

Actual Behavior:

• Currently there isn't any standard coding style getting followed.
• When developers propose any changes in the project it brings inconsistency to the project, since every developer has his/her own convention of coding style.

Would you like to work on this issue?

• Yes
• No

Pluralization Bug When Searching for Query with Only One Result

I'm submitting a ...

• bug report
• feature request

Expected Behavior:

• If I search something up in the engine, and it only has 1 result, I would expect the query to say: "Showing 1 result for: query"

Actual Behavior:

• If I actually do the above, the query responds with "1 results", which is grammatically incorrect.

Steps to Reproduce:

• Go to http://search.opengenus.org/
• Write a query that will get you 1 result, say "binary search"
• Look at the "Showing 1 result" part.

Screenshots (if any):

Would you like to work on this issue?

• Yes
• No

Topic Tags on Main page

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:
Whenever user enters cosmos-search he/she is not aware about topics like bit manipulation,AI etc.So in order to make user's learning path more smooth we can display topics on main page.

Would you like to work on this issue?

• Yes
• No

Copy functionality in the code viewer has error

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:

The copy functionality should correctly copy the code with proper characters.

Expected Behavior:

The code viewer has a bug in the copy functionality. The copied code incorrectly contains &gt etc. in place of > and similar characters.

Actual Behavior:

The coped code should have the characters > etc.

Steps to Reproduce:

-Search 'merge sort',

• View the PHP code
• Copy the code with the button.
• Paste in a text editor ( I have used Gedit in Ubuntu 14 )

Screen shots (if any):

Would you like to work on this issue?

• Yes
• No

Code and settings should be separate

I'm submitting a ... (check one with "x")

• bug report
• feature request

Description:

It is usually a good idea in a Django project to keep the settings separately and not commit those along with the code in the settings.py file (e.g., the SECRET_KEY and ALLOWED_HOSTS, etc.)

Expected Behavior:

The settings should be separated from the code in settings.py file. Python Decouple is a great module for this purpose.

Actual Behavior:

Code is not separated from settings.

Steps to Reproduce:

Just see the settings.py file. It has SECRET_KEY and other important settings committed, which by convention, should not be committed.

Screenshots (if any):

Would you like to work on this issue?

• Yes, definitely
• No