allcapsdev / cvcsv-cli Goto Github PK

Is your feature request related to a problem? Please describe.
The product returned may not be the correct product but may fit within the correct product category, for example: when looking for cosmetic products, the shape & design of a lipstick can be visually similar across brands. This could result in many results being returned which are not the correct brand but are lipsticks, having a way to identify the product being searched for as being a lipstick would be useful.

Describe the solution you'd like
The best place to put this would be in the labels section of the csv. At present, this creates tags based upon the directory structure. Ideally, instead of tag=lipstick it should have category=lipstick.

Describe alternatives you've considered
There isn't really any other place to put this information.

Additional context
N/A

Is your feature request related to a problem? Please describe.
Add a progress bar to show progress through CSV creation.

Describe the solution you'd like
See above

Describe alternatives you've considered
N/A

Additional context
N/A

🚨 The automated release from the develop branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the develop branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Is your feature request related to a problem? Please describe.
The recent change to introduce the category means sadly means the display name also includes the category, this is not the intended behaviour.

Describe the solution you'd like
Remove the category from the display name

Describe alternatives you've considered
N/A

Additional context
N/A

Is your feature request related to a problem? Please describe.
Typing the same values each time is annoying and prone to human error.

Describe the solution you'd like
A config file in order to pre-fill the answers.

Describe alternatives you've considered
ENV vars (which could also work)

Additional context
N/A

Is your feature request related to a problem? Please describe.
Release 2.0.0 introduced the category option for labels but what if we need some other labels?

Example: Brand.

Using the current system of using the directory structure then the brand would be directory 0.

That could be done in the same method as category but it is still limiting to just two labels, when the directory structure could accommodate more options, or maybe a standard tag across the entire set of images that is not tied to the dir structure, no labels or just the current default setting of creating 'tags'.

Describe the solution you'd like
.cvcsvrc:

{
  "bucketName": "the-name-of-the-gs-bucket-the-sample-images-are-stored",
  "csvFileLocation": "where-you-would-like-to-save-the-csv-file",
  "csvFilename": "the-name-of-the-file.csv",
  "labels": {
    "category": 3,
    "brand": 0,
    "wu-tang": "is for the children",
    "tag": true
  },
  "productCategory": "any-of-the-product-categories-GCP-CV-has",
  "productSet": "the-name-of-your-product-set",
  "rootDirectory": "the-root-directory-of-your-images"
}

Tag = true would mean the default behaviour of tags for dir names would also be included, this could be defaults: true instead of tag

Describe alternatives you've considered
Hard coding brand much like the category option at the moment.

Additional context
N/A

Is your feature request related to a problem? Please describe.
With the Dependabot updates to packages, an automated weekly release schedule would be beneficial.

Describe the solution you'd like
Github Actions to do it.

Describe alternatives you've considered
A reminder in my calendar, which I can forget/ignore depending upon work.

Additional context
Also needed for https://github.com/matt-riley/gcp-cv-import

Describe the bug
Error when naming the output file name.

To Reproduce
Steps to reproduce the behavior:

1. Run CLI with no config file
2. Get to 3rd question, add any value
3. Press Enter

Expected behavior
It to work 🤷‍♂

Screenshots

Desktop (please complete the following information):

• OS: macOS
• Version: 10.15.3

Additional context
N/A

Is your feature request related to a problem? Please describe.
Add normalised vertices/bounding poly to the CSV.

Describe the solution you'd like
Using Google Cloud Vision Object Detection

Describe alternatives you've considered
Manual?

Additional context
N/A

Describe the bug
rootDirectory: "./images"

Results in a display name of Images Some Product

To Reproduce
See above

Expected behaviour

The rootDir not to be included in the product name.

Screenshots
N/A

Desktop (please complete the following information):
macOS 10.14.6

Additional context
N/A