PromucFlow_constructor/app/server
Rahul Barwal 7cd941ec6d
chore: Refactors hide embed share setting flag. (#25284)
## Description
As we are deprecating FF4J system in favour of flagsmith. 
This PR renames APP_EMBED_VIEW_HIDE_SHARE_SETTINGS_VISIBILITY to
release_embed_hide_share_settings_enabled
#### PR fixes following issue(s)
Fixes #25232 
> 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?
- [x] Cypress
>
>
#### Test Plan
#### 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
- [x] My code follows the style guidelines of this project
- [x] 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
- [x] My changes generate no new warnings
- [x] 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
2023-07-12 19:19:49 +05:30
..
.run chore: Upgrade to Spring Boot 3.0.1 (#19044) 2023-01-02 19:40:59 +07:00
appsmith-git chore: Applied Spotless formatter (#25173) 2023-07-07 00:43:11 +05:30
appsmith-interfaces feat: activation phase 1 (#25126) 2023-07-12 12:12:16 +05:30
appsmith-plugins fix: fix MsSQL JDBC URL format error (#25094) 2023-07-11 17:44:33 +05:30
appsmith-server chore: Refactors hide embed share setting flag. (#25284) 2023-07-12 19:19:49 +05:30
envs fix: Updated server set up docs to lower confusion from logs (#22926) 2023-05-03 10:17:34 +05:30
mongo-seed Code formatting corrected. 2020-04-20 18:17:25 +05:30
reactive-caching chore: Applied Spotless formatter (#25173) 2023-07-07 00:43:11 +05:30
scripts feat: migrate from org to workspace under phase 3 (#14158) 2022-07-20 17:24:16 +05:30
.gitignore Improve server setup experience documentation (#4441) 2021-05-19 19:29:08 +05:30
build.sh chore: Check Java version in build script (#19531) 2023-01-06 22:20:58 +05:30
buildpack-run.sh Merge branch 'release' into feature/acl-spring-object 2020-04-28 18:13:06 +05:30
docker-compose.yml feat: Git version control functionality with connect to remote, commit, push flows (#8403) 2021-10-20 09:47:34 +00:00
Dockerfile chore: Upgrade to Spring Boot 3.0.1 (#19044) 2023-01-02 19:40:59 +07:00
entrypoint.sh fix: Added JVM arg to opens java.time module to project (#20326) 2023-02-02 17:19:53 +05:30
pom.xml ci: Added pre-commit hook to check for Spotless formatting (#25228) 2023-07-10 11:18:52 +05:30
Procfile Adding the JVM parameter to ensure that java stays within the memory limits set by the container 2019-10-21 12:23:00 +05:30
README.md ci: Modularizing the Github actions workflow for maintainability (#16505) 2022-09-09 01:08:55 +05:30
system.properties chore: Upgrade to Spring Boot 3.0.1 (#19044) 2023-01-02 19:40:59 +07:00

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.