-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow usage of proprietary
license in composer.json
#44
Comments
SychO9
added a commit
that referenced
this issue
Sep 23, 2024
pushed a commit that will fix it for the next version 👍🏼 |
Thank you so much! |
SychO9
added a commit
that referenced
this issue
Nov 23, 2024
* chore: first iteration (frontend changes) * fix: improvements * fix: improvements * fix: improvements * fix: improvements * feat: backend changes * feat: JSON:API migration help * feat: search api migration * chore: visual improvements * feat: continue * chore: improvements * fix: allow proprietary license (#44) * chore: improvements * chore: improvements * chore: improvements * chore: improvements * chore: improvements * chore: improvements * chore: improvements * chore: improvements * chore: improvements * chore: improvements * chore: improvements * chore: improvements * chore: improvements * chore: improvements * chore: improvements * feat: intervention/image * chore: improvements
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With version
@flarum/cli/2.0.0-beta.17 darwin-arm64 node-v20.6.0
it's currently not possible to use any other license than the official SPDX licenses, which in principle makes sense. A workaround for using the CLI is to temporarily use a different, valid SPDX license and change it back after.When trying to use the cli anyways with an invalid SPDX license, such as
proprietary
, the following error is thrown:Therefore, I would propose that
proprietary
is added as an exception and made available to developers working on private extensions. I'm just throwing this idea out there, I have no idea if this can even feasibly be done in this repo.Thoughts?
The text was updated successfully, but these errors were encountered: