Consider having `routes.json` at the top-level

Open
#226 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
web-dev

Research direction

Start by tracing how lib/routes.json is loaded by the project and how browser compatibility affects its location. Check whether moving it to the repository top level preserves the existing behavior; if so, add the move and verify the relevant build or browser workflow, otherwise close the issue as requested.

Written by the indexing model from the issue text.

Description

After #225 the content of the file had to be moved to lib (where all the JS lives for Franklin). However, it's not contirbutor-friendly for the file to remain there instead of being at the top-level.

Question posed is as follows: could we have routes.json at the top-level while being compatible with all browsers?

  • If yes, a PR should add this
  • If no, close this issue
Dominant language
ReScript
Stars
126
Forks
19
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from JuliaAI/DataScienceTutorials.jl

All issues in JuliaAI/DataScienceTutorials.jl

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.