You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rocket.Chat started moving some methods in their API to the Enterprise subscription.
Because of that some tests failed and we started getting this error {'error': 'This is an enterprise feature [error-action-not-allowed]', 'errorType': 'error-action-not-allowed', 'success': False}
We are still talking about getting a key for testing but it might be this is a blocker for people that want to collaborate with the project and won't have the same key to run the tests locally.
Should we remove enterprise-only methods from the wrapper or should we accept contributors can only fully test the API in the CI?
What do you think?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Rocket.Chat started moving some methods in their API to the Enterprise subscription.
Because of that some tests failed and we started getting this error
{'error': 'This is an enterprise feature [error-action-not-allowed]', 'errorType': 'error-action-not-allowed', 'success': False}
We are still talking about getting a key for testing but it might be this is a blocker for people that want to collaborate with the project and won't have the same key to run the tests locally.
Should we remove enterprise-only methods from the wrapper or should we accept contributors can only fully test the API in the CI?
What do you think?
Beta Was this translation helpful? Give feedback.
All reactions