PromucFlow_constructor/app/server
Nilesh Sarupriya 165856e885
chore: remove FF4J (#28653)
## Description
> Remove FF4J 

#### PR fixes following issue(s)
Fixes #24872 
> if no issue exists, please create an issue and ask the maintainers
about this first
>
>
#### Media
> A video or a GIF is preferred. when using Loom, don’t embed because it
looks like it’s a GIF. instead, just link to the video
>
>
#### Type of change
- Chore (housekeeping or task changes that don't impact user perception)

## Testing
>
#### How Has This Been Tested?
- [ ] Manual
- [x] JUnit
- [ ] Jest
- [ ] Cypress
>
>
#### Test Plan
> Add Testsmith test cases links that relate to this PR
>
>
#### Issues raised during DP testing
> Link issues raised during DP testing for better visiblity and tracking
(copy link from comments dropped on this PR)
>
>
>
## Checklist:
#### Dev activity
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] PR is being merged under a feature flag


#### QA activity:
- [ ] [Speedbreak
features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-)
have been covered
- [ ] Test plan covers all impacted features and [areas of
interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-)
- [ ] Test plan has been peer reviewed by project stakeholders and other
QA members
- [ ] Manually tested functionality on DP
- [ ] We had an implementation alignment call with stakeholders post QA
Round 2
- [ ] Cypress test cases have been added and approved by SDET/manual QA
- [ ] Added `Test Plan Approved` label after Cypress tests were reviewed
- [ ] Added `Test Plan Approved` label after JUnit tests were reviewed


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Refactor**
- Simplified the feature flag checking process, removing dependencies on
external libraries.
- Improved error handling in feature flag services for more robust
operation.

- **Bug Fixes**
- Adjusted feature flag refresh logic to ensure accurate status
representation.

- **Tests**
- Updated test cases to align with the new feature flag checking logic
and error handling improvements.

- **Documentation**
- Removed outdated comments and documentation related to the old feature
flag system.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Nilesh Sarupriya <20905988+nsarupr@users.noreply.github.com>
Co-authored-by: Abhijeet <abhi.nagarnaik@gmail.com>
2023-12-12 10:44:58 +05:30
..
.run
appsmith-git fix: Whitelist .MD and .github extensions when checking empty repository (#29301) 2023-12-05 14:12:11 +06:00
appsmith-interfaces fix: Community templates UX issue (#29164) 2023-12-12 09:42:36 +05:30
appsmith-plugins fix: s3 endpoint url field while importing json (#29424) 2023-12-08 11:10:39 +05:30
appsmith-server chore: remove FF4J (#28653) 2023-12-12 10:44:58 +05:30
envs
mongo-seed
reactive-caching chore(deps): Update pf4j to v3.10.0 (#27044) 2023-09-07 08:48:45 +05:30
scripts chore: Delete unused app/server/scripts/node 2023-08-08 06:00:48 +05:30
.gitignore
build.sh
buildpack-run.sh
docker-compose.yml chore: Use new Docker image for dev-time server (#25609) 2023-07-24 09:56:30 +05:30
pom.xml ci: Add retry for JUnit failures in the CI workflow (#29048) 2023-11-23 16:44:57 +05:30
Procfile
README.md
system.properties

Appsmith Server

This is the server-side repository for the Appsmith framework.

For details on setting up your development machine, please refer to this Setup Guide.