Support for # in the parser URL and variable filenames
zawsx opened this issue · 0 comments
https://github.com/kantord/bottoml.in-e imports the just-dashboard module to show one way it can be used with ready-written gists and data files.
I wanted to have a collection of related files in one single gist so thought to look at the code to see how locked into the appended gist URL format you were. It seemed that you detected input file format initially by file extension so I guess the files need to end in .yml or .json etc?
Wasn't sure if the filename 'must' be called dashboard, as in dashboard.yml? I wanted to have pairs in the gist collection of files, t22-yml, t33.yml, t33A.json t33B.json etc
Wanted to group similar graphs in the same gist but that means a location.hash added to the url so a new regexp needed? For instance, I made this gist
https://gist.github.com/zawsx/84c95865d0613ce210a148421815e966
If contains two of your example files,
https://gist.github.com/zawsx/84c95865d0613ce210a148421815e966#file-g22nutri-json
and
https://gist.github.com/zawsx/84c95865d0613ce210a148421815e966#file-t22-yml
Explicit support for hashes might also bring the possibility of adding #myswitch (e.g. #local, #remote, #debug) so as to maybe bring more flexibility to the segment count approach? My localhost test of the bottomline server wouldn't resolve to the pattern I was expecting - localhost:8080/reponame by default, I got confused as localhost:8080/example worked but not localhost:8080/reponame/example