Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "See also" links #27

Merged
merged 2 commits into from
Dec 10, 2020
Merged

Add "See also" links #27

merged 2 commits into from
Dec 10, 2020

Conversation

felixr
Copy link
Contributor

@felixr felixr commented Dec 9, 2020

Adds a new table link that keeps track of links between bindings.

Links are displayed under "See also" above the user contributed examples.

In future be extended to keep track of different types of links (such as 'deprecated by' or
'alias for'). This is why it has the relative generic name links.

The entries for the new table are created via a list in seed.janet.
More entries should be created in the future...

I also added semicolons to schema.sql in order to be able to do sqlite new.db < db/schema.sql.
Was not sure whether this conflicts with any other tooling...

And the PR includes also some small changes to the project.janet. I added dependencies that I needed to get it to run and a I updated the license and author field. These changes are independent of the "see also" change and if you prefer I can leave them out of this PR.

Adds dotenv and sqlite to dependencies.
Adds a new table `link` that keeps track of links between bindings.
Currently the only link is "See also", but this in future be extended to
keep track of different types of links (such as 'deprecated by' or
'alias for').

The entries for the new table are created via a list in `seed.janet`.
Copy link

@pepe pepe left a comment

Choose a reason for hiding this comment

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

LGTM. Not sure about semicolons in SQL. Also later I think some in-app mechanism for adding links, instead of seeding them, would be great.

@swlkr
Copy link
Owner

swlkr commented Dec 10, 2020

I don't think the semicolons will affect anything, but yeah this does look good!

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.

None yet

3 participants