-
Notifications
You must be signed in to change notification settings - Fork 20
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
Rename suites
to projects
#254
Comments
I agree! Although, if it's the very first time the user creates the synthetics code, it's probably not so obvious how they need to organize the test file(including file name). In this case, we can add a help text or a link to the documentation so users know what to do. If we decide to keep this feature, however, we should:
|
Yeah, I wonder, if we remove this option, will a user just copy the code into their project folder, and wonder why it doesn't work? I guess the problem here is that even with the current suite (should change this to project) export option, this still won't work if trying to Maybe we should actually enhance the project export option to include these (even if it sets the location to |
To focus on MMFS, change |
@paulb-elastic should this be pushed to 8.4? |
I agree with @paulb-elastic and have updated the top comment. All we're going to do here is rename |
suites
to projects
Checked this against recent |
AC:
suites
toprojects
(that's the scope of this issue)Original issue text below
We currently let users export javascript for both inline scripts and projects via the UI shown below. The ability to format for projects is confusing to some users. This issue kicks off a discussion on how we can improve this.The more I think about it, the more I think we don't need that feature, for script users they can add their own wrappingjourney statements
, but I want to leave this issue up as a placeholder.The text was updated successfully, but these errors were encountered: