Skip to content
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

[FSSDK-8955] Refac: Replaced all instances of full stack except from changelog file and code files #331

Merged
merged 7 commits into from
Mar 14, 2023

Conversation

mnoman09
Copy link
Contributor

Summary

  • Updated readme file and matched its format with the provided sample readme file.
  • Removed all occurrences of full stack with Optimizely Feature Experimentation

Test plan

All tests should pass.

Issues

@mnoman09 mnoman09 requested a review from a team as a code owner March 10, 2023 16:54
@mnoman09 mnoman09 removed their assignment Mar 10, 2023
Copy link
Contributor

@griffincox-optimizely griffincox-optimizely left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you need to add Prerequisites and/or Requirements sections (see template.md on story)

Let's talk about breaking apart the "Use the C#SDK" and "Development" sections...

OptimizelySDK.DemoApp/README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
Copy link
Contributor

@griffincox-optimizely griffincox-optimizely left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one last change then it LGTM.

README.md Outdated Show resolved Hide resolved
Co-authored-by: Griffin Cox <[email protected]>
README.md Outdated

Optimizely Full Stack is A/B testing and feature flag management for product development teams. Experiment in any application. Make every feature on your roadmap an opportunity to learn. Learn more at https://www.optimizely.com/platform/full-stack/, or see the [documentation](https://docs.developers.optimizely.com/experimentation/v4.0.0-full-stack/docs/welcome).
Optimizely Feature Experimentation is an A/B testing and feature management for product development teams, letting you experiment at every step. Using Optimizely Feature Experimentation allows for every feature on your roadmap to be an opportunity to discover hidden insights. Learn more at [Optimizely.com](https://www.optimizely.com/products/experiment/feature-experimentation/), or see the [developer documentation](https://docs.developers.optimizely.com/experimentation/v4.0.0-full-stack/docs/welcome).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Optimizely Feature Experimentation is an A/B testing and feature management for product development teams, letting you experiment at every step. Using Optimizely Feature Experimentation allows for every feature on your roadmap to be an opportunity to discover hidden insights. Learn more at [Optimizely.com](https://www.optimizely.com/products/experiment/feature-experimentation/), or see the [developer documentation](https://docs.developers.optimizely.com/experimentation/v4.0.0-full-stack/docs/welcome).
Optimizely Feature Experimentation is an A/B testing and feature management tool for product development teams, letting you experiment at every step. Using Optimizely Feature Experimentation allows for every feature on your roadmap to be an opportunity to discover hidden insights. Learn more at [Optimizely.com](https://www.optimizely.com/products/experiment/feature-experimentation/), or see the [developer documentation](https://docs.developers.optimizely.com/experimentation/v4.0.0-full-stack/docs/welcome).

README.md Outdated

Optimizely Full Stack is A/B testing and feature flag management for product development teams. Experiment in any application. Make every feature on your roadmap an opportunity to learn. Learn more at https://www.optimizely.com/platform/full-stack/, or see the [documentation](https://docs.developers.optimizely.com/experimentation/v4.0.0-full-stack/docs/welcome).
Optimizely Feature Experimentation is an A/B testing and feature management for product development teams, letting you experiment at every step. Using Optimizely Feature Experimentation allows for every feature on your roadmap to be an opportunity to discover hidden insights. Learn more at [Optimizely.com](https://www.optimizely.com/products/experiment/feature-experimentation/), or see the [developer documentation](https://docs.developers.optimizely.com/experimentation/v4.0.0-full-stack/docs/welcome).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"developer documentation" has two separate links for each word, not sure why (syntax looks correct). Possible to make it one link for the term?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think there is any other way. this is the only syntax which I think that can be used.

README.md Outdated

See the Optimizely Full Stack C# SDK [developer documentation](https://docs.developers.optimizely.com/experimentation/v4.0.0-full-stack/docs/csharp-sdk) to learn how to set up your first Full Stack project and use the SDK.
## Use the Csharp SDK
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Use the Csharp SDK
## Use the C# SDK

README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Outdated
### Installing the SDK
## Get Started

Refer to the [Csharp SDK's developer documentation](https://docs.developers.optimizely.com/experimentation/v4.0.0-full-stack/docs/csharp-sdk) for detailed instructions on getting started with using the SDK.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit:

Suggested change
Refer to the [Csharp SDK's developer documentation](https://docs.developers.optimizely.com/experimentation/v4.0.0-full-stack/docs/csharp-sdk) for detailed instructions on getting started with using the SDK.
Refer to the [C# SDK's developer documentation](https://docs.developers.optimizely.com/experimentation/v4.0.0-full-stack/docs/csharp-sdk) for detailed instructions on getting started with using the SDK.

README.md Outdated
The sample project contains unit tests as well which can be run from the built-in Visual Studio Test Runner.

### Contributing
## Contributing
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Contributing
## SDK Development
### Contributing

The sample project contains unit tests as well which can be run from the built-in Visual Studio Test Runner.

### Contributing
## Contributing

Please see [CONTRIBUTING](CONTRIBUTING.md).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change line 223 to ### Third Party Licenses

@@ -10,7 +10,7 @@ updatedAt: "2020-01-28T21:53:11.290Z"
"title": "Overview"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change looks good, but md file as a whole doesn't seem to be rendering properly. Could you please take a look?

@@ -5,7 +5,7 @@ hidden: false
createdAt: "2019-09-12T13:44:04.059Z"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also doesn't seem to be rendering properly, could you please double check?

@@ -38,7 +38,7 @@ jobs:
TRAVIS_COM_TOKEN: ${{ secrets.TRAVIS_COM_TOKEN }}

fullstack_production_suite:
name: Run Full Stack Compatibility Suite
name: Run Optimizely Feature Experimentation Compatibility Suite
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Totally fine with the change so long as you don't think it would be confusing since we still call the test suite by "FSC".

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure are we are going to rename FSC as well?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Funny. What can be a good name to replace it internally. FXC? @russell-loube-optimizely

@@ -91,7 +91,7 @@ The table lists other other Optimizely functionality that may be triggered by us
"h-0": "Functionality",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also not rendering properly?

Copy link
Contributor

@jaeopt jaeopt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -38,7 +38,7 @@ jobs:
TRAVIS_COM_TOKEN: ${{ secrets.TRAVIS_COM_TOKEN }}

fullstack_production_suite:
name: Run Full Stack Compatibility Suite
name: Run Optimizely Feature Experimentation Compatibility Suite
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Funny. What can be a good name to replace it internally. FXC? @russell-loube-optimizely

Copy link
Contributor

@russell-loube-optimizely russell-loube-optimizely left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mikechu-optimizely
Copy link
Contributor

I didn't even think about FSC and FXC naming now @jaeopt Good call out

@mikechu-optimizely
Copy link
Contributor

@mnoman09 The linter is not happy with the markdown. Should we disable validation or go ahead and clean based on the rules?

@mikechu-optimizely
Copy link
Contributor

I disabled super-linter's markdown linting. Waiting for FSC to finish successfully.

@mikechu-optimizely
Copy link
Contributor

@mnoman09 Should I go ahead and squash+merge?

@@ -38,7 +37,7 @@ jobs:
TRAVIS_COM_TOKEN: ${{ secrets.TRAVIS_COM_TOKEN }}

fullstack_production_suite:
name: Run Full Stack Compatibility Suite
name: Run Optimizely Feature Experimentation Compatibility Suite
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mnoman09 I wonder if @russell-loube-optimizely is on point here. The ping is not completing b/c we've renamed the job. Maybe revert this particular instance.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No this does not have to do with the issue because build uses fullstack_production_suite as ID and it is running fine.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool. I'll merge then.

@mnoman09 mnoman09 closed this Mar 14, 2023
@mnoman09 mnoman09 reopened this Mar 14, 2023
@mnoman09 mnoman09 merged commit 5f16357 into master Mar 14, 2023
@mnoman09 mnoman09 deleted the mnoman/mdFilesUpdate branch March 14, 2023 19:59
mnoman09 added a commit that referenced this pull request Mar 14, 2023
…changelog file and code files (#331)

* Replaced all instances of full stack except from changelog file and code files

Co-authored-by: Griffin Cox <[email protected]>

* [FSSDK-8955] Do not lint markdown for now

* [FSSDK-8955] Remove VALIDATE_MARKDOWN

---------

Co-authored-by: mnoman09 <[email protected]>
Co-authored-by: Griffin Cox <[email protected]>
Co-authored-by: Mike Chu <[email protected]>
(cherry picked from commit 5f16357)
mikechu-optimizely pushed a commit that referenced this pull request Mar 15, 2023
…changelog file and code files (#331)

* Replaced all instances of full stack except from changelog file and code files

Co-authored-by: Griffin Cox <[email protected]>

* [FSSDK-8955] Do not lint markdown for now

* [FSSDK-8955] Remove VALIDATE_MARKDOWN

---------

Co-authored-by: mnoman09 <[email protected]>
Co-authored-by: Griffin Cox <[email protected]>
Co-authored-by: Mike Chu <[email protected]>

(cherry picked from commit 5f16357)
mnoman09 added a commit that referenced this pull request Mar 16, 2023
…changelog file and code files (#331)

* Replaced all instances of full stack except from changelog file and code files

Co-authored-by: Griffin Cox <[email protected]>

* [FSSDK-8955] Do not lint markdown for now

* [FSSDK-8955] Remove VALIDATE_MARKDOWN

---------

Co-authored-by: mnoman09 <[email protected]>
Co-authored-by: Griffin Cox <[email protected]>
Co-authored-by: Mike Chu <[email protected]>
(cherry picked from commit 5f16357)
(cherry picked from commit 887166e)
mnoman09 added a commit that referenced this pull request Mar 16, 2023
* chore : updated prefix of ticket-check action (#314)

(cherry picked from commit 678c6fd)

* chore: Fix and Reconfigure GitHub Actions (#319)

* Fix <return> method doc for IsFeatureEnabled (#329)

* [FSSDK-8938] chore: Updated newtonsoft.Json version and NjsonSchema version (#330)

* [FSSDK-8955] Refac: Replaced all instances of full stack except from changelog file and code files (#331)

* Replaced all instances of full stack except from changelog file and code files

Co-authored-by: Griffin Cox <[email protected]>

* [FSSDK-8955] Do not lint markdown for now

* [FSSDK-8955] Remove VALIDATE_MARKDOWN

---------

Co-authored-by: mnoman09 <[email protected]>
Co-authored-by: Griffin Cox <[email protected]>
Co-authored-by: Mike Chu <[email protected]>
(cherry picked from commit 5f16357)
(cherry picked from commit 887166e)

* [FSSDK-8955] Refac: Replaced all instances of full stack  from code comments and in nuspec except owner. (#332)

(cherry picked from commit 2a5b19c)

* [FSSDK-8955] chore: prepare for release 3.11.2 (#333)

* [FSSDK-8955] chore: prepare for release 3.11.2

* Nit fixed

---------

Co-authored-by: mnoman09 <[email protected]>
(cherry picked from commit e620c08)

* updated release date to 16th March

---------

Co-authored-by: Muhammad Shaharyar <[email protected]>
Co-authored-by: Mike Chu <[email protected]>
Co-authored-by: mnoman09 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants