fossapps / feature.manager Goto Github PK

Currently, someone can stop with "ChangeSettings", then create a new run, then stop the first run with "AllB" and will end up with 2 running items, that should be prevented

currently if service is unavailable, list of feature is initialized using null and throws a null reference exception, we need to initialize with a empty list.

🚨 The automated release from the master 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 master 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.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://[secure]@github.com/fossapps/Feature.Manager.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨

Your semantic-release bot 📦🚀

looks like the searialize as string isn't happening on dotnet core

currently there's no list of features endpoint, introduce 1 for frontend

https://github.com/fossapps/Micro.Starter/pull/25/files#diff-9b27a220148e9dc2a96ad951282cc1e6d1e59d536cd93175ff7631b71078bafeR38-R42

Is your feature request related to a problem? Please describe.
When we want to say open this feature for internal employees, there's no way to do this, (or github style, enabling something)

Describe the solution you'd like
Still needs to do some research on what structure would be the best, it should be scalable, client needs to be able to overwrite, but there SHOULD be a way not to let users opt in, but only do allocation as well.

currently publish step runs immediately, it needs to wait for sdk generation and test

Use either request headers, or request URLs (or maybe cookie?)

currently all B isn't working

https://github.com/fossapps/Micro.Starter/pull/25/files#diff-9b27a220148e9dc2a96ad951282cc1e6d1e59d536cd93175ff7631b71078bafeR38-R42

• add feature run for a feature which doesn't exist
• it shouldn't work, but it does