Library name can be different than filename

Open
  • Is something wrong?
#42 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Review the current output model and the related discussion in issue #41. Trace how library names and module filenames are represented, then define an output shape that makes their relationship unambiguous. Done means users can tell which file contains each library while preserving the module-file information.

Written by the indexing model from the issue text.

Description

It's not fully supported now - output contains library name but filename is discarded. This may create confusion - we need to remodel output so it's clear what file contains what library.

Possibly related #41 (we could model it so we show that library is created from given module, while still showing module files)

Dominant language
Python
Stars
14
Forks
1
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 MarketSquare/robotframework-sherlock

All issues in MarketSquare/robotframework-sherlock

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.