nitzano / enum-converter

Convert enums from one language to another

enum-converter's Issues

Add wallabyjs support

Describe the solution you'd like

Add wallabyjs support (placeholder for closed issue)

Is your feature request related to a problem? Please describe.

Additional context

None

Do not compile tests for production

• Move all specs to tests folders
• Do not compile tests in production

Add coverage tests

Is your feature request related to a problem? Please describe.

No

Describe the solution you'd like

Adding coverage tests for the project (jest)

Additional context

Add semantic release support

Add semantic release support

Revive vercel websites

Revive the vercel app

Is your feature request related to a problem? Please describe.

Additional context

None

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

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

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 fix 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 are 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.

---

The release 1.4.7 on branch master cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.4.6 <1.4.7 can be published from branch master.

The following commits are responsible for the invalid release:

• chore: deploy (e3bce70)
• fix: fixed readme again (29d2ced)
• chore: update readme (74c7418)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch master with git revert or git reset.

A valid branch could be next.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Fix travis ci

make the travis intergation work again

Return version from enum-converter package

Describe the solution you'd like

Is your feature request related to a problem? Please describe.

Additional context

None

Add go dumper

Describe the solution you'd like

Is your feature request related to a problem? Please describe.

Additional context

None

Upgrade to yarn v2

Describe the solution you'd like

Is your feature request related to a problem? Please describe.

Additional context

None

Move to @vercel/node

Release enum converter 1.3.7-alpha

Release first alpha

Move __tests__ folder into src

• Move packages/enum-converter/__tests__ to

packages/enum-converter/src

• Change rootDir to ./src to emit flat files

• Fix the cli reference in

packages/enum-converter/package.json

Add graphql support

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

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

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 fix 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 are 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.

---

The release 1.4.7 on branch master cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.4.6 <1.4.7 can be published from branch master.

The following commits are responsible for the invalid release:

• fix: fixed readme again (29d2ced)
• chore: update readme (74c7418)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch master with git revert or git reset.

A valid branch could be next.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Sort enums in file by number of values

Describe the solution you'd like

We would like to add the ability to sort enums in file by the number of values
they contain inside of them. Sorting should be both ascending and descending.
Sorting by this option should be enabled both in cli and api.

Is your feature request related to a problem? Please describe.

No, a new feature

Additional context

None.

Allow the library to be consumed from client side

Describe the solution you'd like

We want the o use enum-converter from client-side, for that there
there should be added a solution for consuming from web (currently buggy).
Solution can be either be by code or adding appropriate documentation.

Is your feature request related to a problem? Please describe.

Yes, enum converter cannot be consumed/compiled from web applications.

Additional context

Upgrade babel polyfill

Describe the solution you'd like

Upgrade "@babel/polyfill" package

Is your feature request related to a problem? Please describe.

Additional context

None

Style string enum values

Describe the solution you'd like

We would like to style string values in enums by StringStyle in the same
way we do for Enum Names and Keys. Please make sure this only applies
to string values and should be enabled in all dumpers.

Is your feature request related to a problem? Please describe.

Additional context

Add java dumper

Is your feature request related to a problem? Please describe.

Yes, there is only java parser at the moment without the ability to dump to java.

Describe the solution you'd like

A java dumper.

Additional context

Update version

Update enumc version to work again

Upgrade to babel 7

Upgrade babel version to 7