sitespeedio / sitespeedio/sitespeed.io

How to get --groupAlias and urlAlias in a file to work together

Open
#3,097 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
5k
Forks
624
Avg merge
4h 8m
Merged PRs (30d)
2

Description

Hi there, I currently have a file with 3 urls in it that I am testing against my site, of which I am using a urlAlias in the file. This is setup as below (called sitespeedio_urls.txt)

https://www.dae.mn home
https://www.dae.mn/about-us/ about-us
https://www.dae.mn/our-approach/ our-approach

Our domain name is www.dae.mn, but our company name is Daemon. We're using the Grafana boards where the domain is referencing the group in Graphite, which in this case is www_dae_mn. We would like to override this to be Daemon as it makes it more human readable. Looking at the documentation I believe you can do this with the --groupAlias, but when I pass this on the command line like: docker-compose run sitespeed.io --config sitespeedio_config.json sitespeedio_urls.txt --groupAlias Daemon I get an error stating that the number of Group Aliases does not match the number of URLs.
Is there a way of pushing the groupAlias into the text file like the urlAlias, or some other way to satisfy my requirement?

Thanks!

shaqb

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the command with sitespeedio_urls.txt, --groupAlias Daemon, and the three URL aliases shown in the report. Trace how command-line group aliases and per-line URL aliases are parsed and validated; done means the requested alias combination works without the group-count error and produces the intended human-readable group name.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli, observability
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.